Error in deployment for environment test

Google Cloud Apigee
1

I am getting following error while deploying the proxy in test environment:

Error in deployment for environment test.

The revision is deployed and traffic can flow, but flow may be impaired. Call timed out; either server is down or server is not reachable

I tried following solution, but had no success:

  1. https://community.apigee.com/questions/7759/does-anyone-has-this-error-on-apigee-edge-today.html

  2. https://community.apigee.com/questions/6231/deployment-error-when-trying-to-deploy-api-proxy-s.html

  3. https://community.apigee.com/questions/4733/api-proxies-deployment-revisions-in-test-and-prod.html

Can you please help me getting the API proxy deployed correctly?

–

Thanks,

Gajanan

2 Likes
2

Hi @Gajanan Khandake,

Try this, https://community.apigee.com/answers/7777/view.html or create a support ticket here,https://pages.apigee.com/request-support-general.html

Thanks,

3

If you are pointing to following post call then it’s not clear. Can you please add more details like where to point this post call? I have correctly replaced the entities mentioned in {} brackets.

POST /v1/o/{orgid}/apis/{api}/revisions/{rev}/deployments?action=undeploy&env={env}&force=true-H "Content-Type: application/octet-stream"
4

It should point to ‘https://api.enterprise.apigee.com’ in case of cloud,

‘http://management-server-ip:8080/’ in case of private cloud

5

Tried following call, received “No response received”

POST [https://api.enterprise.apigee.com/v1/o/{my_org}/apis/{my_api}/revisions/9/deployments?action=undeploy&env=test&force=true](https://api.enterprise.apigee.com/v1/o/{my_org}/apis/{my_api}/revisions/9/deployments?action=undeploy&env=test&force=true)
6

Today, I am getting following error while re-deploying proxy in test / prod environment. I have replaced the organization with {my_org} and proxy with {my_proxy} in following error message.

Error Deploying Revision 9 to testcom.apigee.zookeeper.ZooKeeperException{ code = zookeeper.ErrorCreatingPath, message = Error while creating path : /organizations/{my_org}/environments/test/apiproxies/{my_proxy}/revisions/9/statuses/3cb53ac7-7474-4f9a-aa37-86ca9796fdb1/status, associated contexts = []}.
7

This issue is solved. I can deploy / un-deploy proxies. Thanks!

Mean time can I know what was the root cause and how it got solved?

1 Like
8

Did you get to the root cause of this issue? I’m experiencing the same problems.

9

where we need to test the POST request. Can anyone help on this

10

I am also experiencing this problem

11

Same problem here:

I’ve had the problem off and on, so I created a completely new account and everything was fine until today. I don’t think it’s code.

Error in deployment for environment test. The revision is deployed and traffic can flow, but flow may be impaired. Call timed out; either server is down or server is not reachable

12

In the comments I see some requests for root cause on this issue. While I can not speak to your specific experience, generally these type of issues come down to memory related errors on message processors which can be the result of many simultaneous deployments by multiple users, or very large bundles with many javascript policies.

For paid customers opening a ticket with the Apigee support team is your best bet to get these resolved in a timely manner.

13

Summarized answer can be found here: https://community.apigee.com/articles/8352/revision-is-deployed-and-traffic-can-flow-but-flow.html

14

I am having same error on Friyday @Gajanan Khandake. If you get some solution then please share. Besides this I got one more error during going to trace window.

15

So, if you don’t have a paid account, support will not help?

OK. Are there any other options here? Is there any way a particular message processor can be taken out when deploying? Is there a particular time of day that has less load so will be more likely to deploy? I need to be able to trace my API.