Bug 1295569 - overcloud stack create fails but 'openstack overcloud deploy' exits with status 0
Summary: overcloud stack create fails but 'openstack overcloud deploy' exits with stat...
Keywords:
Status: CLOSED DUPLICATE of bug 1370527
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-tripleoclient
Version: 8.0 (Liberty)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 10.0 (Newton)
Assignee: Julie Pichon
QA Contact: Ola Pavlenko
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-04 21:46 UTC by Steve Linabery
Modified: 2017-05-31 01:13 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-17 12:54:49 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
output from openstack overcloud deploy (58.47 KB, text/plain)
2016-01-04 21:46 UTC, Steve Linabery
no flags Details

Description Steve Linabery 2016-01-04 21:46:16 UTC
Created attachment 1111567 [details]
output from openstack overcloud deploy

Description of problem:
In a virthost-based OSP8 poodle CI run, I am seeing 'openstack overcloud deploy' exit 0 even though the stack is not created. Overcloud deployment log attached.

Comment 3 Mike Burns 2016-04-07 21:03:37 UTC
This bug did not make the OSP 8.0 release.  It is being deferred to OSP 10.

Comment 6 Jason E. Rist 2016-10-14 22:25:44 UTC
Is this still an issue?

Comment 7 Julie Pichon 2017-02-17 12:54:49 UTC
I will mark this as a duplicate of bug 1370527 as the other bug is seeing more activity. If you disagree with this or the resolution though, please feel free to reopen or open a new one.

Also, if you have a set of templates and/or steps that clearly help to reproduce the failure case with the wrong exit code, that would be tremendously helpful. I suspect there might be different failure paths with this problem.

*** This bug has been marked as a duplicate of bug 1370527 ***


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