Bug 1474367 - splitstack: paunch does not check if docker server is installed and still waiting for a time out
splitstack: paunch does not check if docker server is installed and still wai...
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-heat-agents (Show other bugs)
13.0 (Queens)
Unspecified Unspecified
medium Severity medium
: ---
: 13.0 (Queens)
Assigned To: Steve Baker
Gurenko Alex
: Triaged
Depends On:
  Show dependency treegraph
Reported: 2017-07-24 09:11 EDT by Gurenko Alex
Modified: 2017-10-20 08:52 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-10-20 08:52:23 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Gurenko Alex 2017-07-24 09:11:53 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

Actual results:

Deployment fails after ~30 min with a timeout

Expected results:

Deployment fails right away with respective message if docker server is not installed on overcloud nodes

Additional info:
Comment 1 Dan Prince 2017-10-20 08:48:50 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.