Bug 1295569

Summary: overcloud stack create fails but 'openstack overcloud deploy' exits with status 0
Product: Red Hat OpenStack Reporter: Steve Linabery <slinaber>
Component: python-tripleoclientAssignee: Julie Pichon <jpichon>
Status: CLOSED DUPLICATE QA Contact: Ola Pavlenko <opavlenk>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.0 (Liberty)CC: abregman, hbrock, jcoufal, jpichon, jrist, jslagle, mburns, rhel-osp-director-maint, slinaber, srevivo, whayutin
Target Milestone: ---Keywords: Automation, AutomationBlocker, Triaged, ZStream
Target Release: 10.0 (Newton)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-02-17 12:54:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
output from openstack overcloud deploy none

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 ***