You're viewing Apigee Edge documentation.
View Apigee X documentation.
Error text
Error in deployment for environment test. The revision is deployed, but traffic cannot flow. Error while fetching children for path
If the message includes the words traffic cannot flow, it means that the proxy could not be deployed to ANY available Message Processors or Routers.
If the message says traffic can flow, but flow may be impaired, it means the proxy might have been deployed to some, but not to all available Message Processors or Routers (a partial deployment).
Example error
Error in deployment for environment prod.
The revision is deployed, but traffic cannot flow. com.apigee.repository.RepositoryException{ code = repository.zookeeper.UnExpectedError, message = Unexpected error Error while fetching children for path : /organizations/myorg/environments/prod/apiproxies/test/revisions, associated contexts = []};
Cause
This error indicates a problem related to an internal Apigee Edge component called Zookeeper. The typical cause for this error is network connectivity issue between the Message Processor and ZooKeeper.
What you can do
Edge Private Cloud
If you are on Edge Private Cloud, you may be able to diagnose and resolve this problem yourself. For troubleshooting instructions, go to the Edge Public Cloud Troubleshooting Guide and locate the section that describes this error. If the problem persists, contact Apigee Support.
Edge Public Cloud
If you are on Edge Public Cloud, you will probably need expert help from
Apigee to resolve this error. Please contact Apigee Support. If you are using a trial account, post the issue the Apigee Community. See also the steps outlined in
the Troubleshooting section.
Troubleshooting
For Cloud customers, check the Apigee status page for outages
Deployment errors can occur when there is an outage in Edge for the Cloud. Use the following URL to check the current Edge status to see if there is an outage: https://status.apigee.com
Force undeploy and redeploy
In some cases, undeploying and redeploying the proxy revision will correct the problem. Apigee recommends that you do a forced undeploy using the Deployments API with the parameter force=true. If the forced undeploy works, try redeploying the proxy. If the problem persists, contact Apigee Support.