Bug 1359864 - Openstack deployment fails with CREATE_FAIL (timeout)
Summary: Openstack deployment fails with CREATE_FAIL (timeout)
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Quickstart Cloud Installer
Classification: Red Hat
Component: doc-Release_Notes
Version: 1.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ga
: 1.0
Assignee: Julie
QA Contact: James Olin Oden
URL:
Whiteboard:
Depends On:
Blocks: 1298742
TreeView+ depends on / blocked
 
Reported: 2016-07-25 14:53 UTC by Jason Montleon
Modified: 2016-09-14 10:25 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1298742
Environment:
Last Closed: 2016-09-14 10:25:27 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jason Montleon 2016-07-25 14:53:45 UTC
We have no way to validate the Neutron public interface when doing an osp deployment. This should probably be documented so that users understand this and don't have unrealistic expectations.

+++ This bug was initially created as a clone of Bug #1298742 +++

Description of problem:

OpenStack deployment failed with CREATE_FAIL (timeout)

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

RHCI-6.0-RHEL-7-20160113.t.1
RHCIOOO-7-RHEL-7-20160113.t.8

How reproducible:

100%

Steps to Reproduce:
1. Install ISOs
2. Run fusor install scripts
3. Enter information for deployment with wrong "External Network Interface" in Configure Overcloud
4. Wait until Satellite deployment is finished
5. Wait until 25% in RHELOSP deployment

Actual results:

No error for External Network Interface
ERROR: deployment failed with status: CREATE_FAILED and reason: Create timed out

Expected results:

Error during External Network Interface
Successful deployment

Additional info:

No way of correct and resume, must start from scratch.

Since External Network Interface is using the consistent network device naming (non-ethx), checking for ethx and reporting an error would be one solution.

--- Additional comment from Thom Carlin on 2016-07-01 08:57:23 EDT ---

For QCI 1.2, entered nic7 as "External Network Interface" in "Configure Overcloud"

Receive:
"{"displayMessage":"Task 02ff3cec-84cc-4f2a-8b5d-7088d527d104: RestClient::InternalServerError: 500 Internal Server Error","errors":["Task 02ff3cec-84cc-4f2a-8b5d-7088d527d104: RestClient::InternalServerError: 500 Internal Server Error"]}"

Failed QA

--- Additional comment from Jason Montleon on 2016-07-13 13:16:34 EDT ---

Does nic7 exist? We have absolutely no way to tell in advance how many interfaces exist. If you put in garbage data here expect a failed deployment.

If the systems do in fact have 7 nics it would be helpful to see the /var/log/messages from the overcloud nodes

as root on your undercloud
sudo su - stack
source stackrc
nova server-list
ssh heat-admin@<ip-address-for-one-of-the-servers-listed-in-cmd-above>
sudo su -

Looking at /var/log/messages you'd normally see messages similar to:
nic2 mapped to: eth1

In your case you'd of course be looking for nessages about nic7

--- Additional comment from Red Hat Bugzilla Rules Engine on 2016-07-20 16:06:10 EDT ---

Since this issue was entered in bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release.

--- Additional comment from Red Hat Bugzilla Rules Engine on 2016-07-20 16:06:10 EDT ---

Since this issue was entered in bugzilla with the target milestone set to ga, the bug has been triaged and approved for inclusion in the QCI 1.0 release.  The qci-1 release flag has been set to +.

--- Additional comment from Red Hat Bugzilla Rules Engine on 2016-07-21 15:34:28 EDT ---

Since this issue was entered in bugzilla with the target milestone set to ga, the bug has been triaged and approved for inclusion in the QCI 1.0 release.  The qci-1 release flag has been set to +.

--- Additional comment from Red Hat Bugzilla Rules Engine on 2016-07-21 15:59:16 EDT ---

Since this issue was entered in bugzilla with the target milestone set to ga, the bug has been triaged and approved for inclusion in the QCI 1.0 release.  The qci-1 release flag has been set to +.

--- Additional comment from Red Hat Bugzilla Rules Engine on 2016-07-21 16:10:29 EDT ---

Since this issue was entered in bugzilla with the target milestone set to ga, the bug has been triaged and approved for inclusion in the QCI 1.0 release.  The pm_ack, qa_ack, and devel_ack flags have been set to +.

Comment 3 James Olin Oden 2016-08-18 14:06:39 UTC
The phrase "Ensure to" is awkward English.   A better wording would be "Be sure to".

Also, "...validate if the interface is available." should change to "...validate that the interface is available."   Otherwise the sentence is ambiguous as one has to determine from context if "if" is being used as a conditional on QCI  validating or that QCI does not validate for the existence of the interface (the latter being the correct interpretation in this case).

Comment 5 James Olin Oden 2016-08-24 13:15:17 UTC
Verified in version 1.0 of the document.


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