Bug 1474367 - splitstack: paunch does not check if docker server is installed and still waiting for a time out
Summary: splitstack: paunch does not check if docker server is installed and still wai...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-heat-agents
Version: 13.0 (Queens)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 13.0 (Queens)
Assignee: Steve Baker
QA Contact: Gurenko Alex
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-24 13:11 UTC by Gurenko Alex
Modified: 2017-10-20 12:52 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-10-20 12:52:23 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Gurenko Alex 2017-07-24 13:11:53 UTC
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
3. 

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 12:48:50 UTC
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.