Red Hat Bugzilla – Bug 1474367
splitstack: paunch does not check if docker server is installed and still waiting for a time out
Last modified: 2017-10-20 08:52:23 EDT
Description of problem: if docker is not installed on the overcloud during overcloud deployment paunch still tries to apply configuration in a loop until time out reached without checking whether docker is even there
Version-Release number of selected component (if applicable):
How reproducible: 100%
Steps to Reproduce:
1. Currently docker is not installed along with python-heat-agents*
2. Try deploying openstack with splitstack
Deployment fails after ~30 min with a timeout
Deployment fails right away with respective message if docker server is not installed on overcloud nodes
I think we've worked around this for OSP12 by requiring the docker services template (puppet/services/docker.yaml).
Adding a more robust check in paunch is a worthwhile thing to do but could perhaps wait until OSP13.