When using the simple bootstrap with docker, new deployments can become stuck in an 'Initializing' state if the celery process for create_deployment_environment times out.
This deployment cannot then be removed through the UI.
This can be reproduced by performing a simple deployment where iptables is set to DROP (not tested with REJECT) traffic from the docker container to the IP address cloudify manager is set to be on (e.g. the IP address on eth0 in a single interface system). It appears that celery uses the 'public' IP of the cloudify server to connect, but times out and this error is not handled.
When using the simple bootstrap with docker, new deployments can become stuck in an 'Initializing' state if the celery process for create_deployment_environment times out.
This deployment cannot then be removed through the UI.
This can be reproduced by performing a simple deployment where iptables is set to DROP (not tested with REJECT) traffic from the docker container to the IP address cloudify manager is set to be on (e.g. the IP address on eth0 in a single interface system). It appears that celery uses the 'public' IP of the cloudify server to connect, but times out and this error is not handled.