@raasdex This can possibly happen if the deployment fails one or more MPs or routers during the deployment. So if you make an API call to the deployments resource, you should see something like this:
curl -v https://api.e2e.apigee.net/v1/o/{id}/e/{env}/apis/test/deployments
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<APIProxyDeployment name="test">
<Environment>test</Environment>
<Organization>nginx</Organization>
<Revision xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="revisionStatusInEnvironment" name="1">
<Configuration>
<BasePath>/</BasePath>
</Configuration>
<Server xsi:type="serverDeploymentStatus">
<Error>Call timed out; either server is down or server is not reachable</Error>
<UUID>xxxx-yyy-iiii-zzz</UUID>
<Status>error</Status>
<Type>message-processor</Type>
</Server>
<Server xsi:type="serverDeploymentStatus">
<Error>Call timed out; either server is down or server is not reachable</Error>
<UUID>abc-12312---</UUID>
<Status>error</Status>
<Type>message-processor</Type>
</Server>
<Server xsi:type="serverDeploymentStatus">
<UUID>xyz-123</UUID>
<Status>deployed</Status>
<Type>router</Type>
</Server>
<Server xsi:type="serverDeploymentStatus">
<UUID>123-xyz-234..</UUID>
<Status>deployed</Status>
<Type>router</Type>
</Server>
<State>error</State>
</Revision>
</APIProxyDeployment>
There are few reasons why this can happen, if the management server is not able to reach the message-processor or router, the router/mp, is too busy or under heavy load, scheduled downtimes or code deployments in progress etc.
To recover from you might want to do a force undeploy. Here's the curl command for it:
curl -v "https://api.e2e.apigee.net/v1/o/{id}/apis/test/deployments?action=undeploy&env=test&force=true"And then try to re-deploy. If you are still stuck with the same error, it probably means that the server has gone bad or something else is wrong which needs the apigee operations team to take a look. At this point, you might have to open a support ticket and get it fixed.
LinkedIn
Twitter
