Bug 1374483 - openshift-on-openstack: ansible setup play timing issue
Summary: openshift-on-openstack: ansible setup play timing issue
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.2.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Sylvain Baubeau
QA Contact: Johnny Liu
URL:
Whiteboard:
Depends On:
Blocks: 1356451
TreeView+ depends on / blocked
 
Reported: 2016-09-08 19:41 UTC by Judd Maltin
Modified: 2016-12-08 22:23 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-09 13:53:59 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Github 212 0 None None None 2016-09-08 19:41:18 UTC

Description Judd Maltin 2016-09-08 19:41:18 UTC 
Description of problem:

Upon initial deployment of OpenShift on OpenStack, system fails to await full execution of cloud-init on all deployed openshift nodes before executing openshift-ansible main.yaml (deploy entire cluster.)

All reproduction and debugging information here:

https://github.com/redhat-openstack/openshift-on-openstack/issues/212


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 Judd Maltin 2016-09-08 19:43:56 UTC 
Docs people: Sorry for posting under documentation.  I was instructed my management to post under OpenStack - and no relevant component is available.
Comment 3 Karl Hastings 2016-09-08 20:09:56 UTC 
Judd,

I've moved the Product to OpenShift Container Platform/Installer as I believe that more accurately reflects the situation.  

Please let me know if you feel it should be filed elsewhere.

-Karl
Comment 4 Judd Maltin 2016-09-09 13:53:59 UTC 
Thanks for the proper classification, Karl.

The bug has been closed, resolved upstream.
Note You need to log in before you can comment on or make changes to this bug.