Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1737759

Summary: Wrong return code of tempest cleanup
Product: Red Hat OpenStack Reporter: Martin Kopec <mkopec>
Component: openstack-tempestAssignee: Chandan Kumar <chkumar>
Status: CLOSED ERRATA QA Contact: Martin Kopec <mkopec>
Severity: medium Docs Contact:
Priority: medium    
Version: 15.0 (Stein)CC: apevec, chkumar, lhh, slinaber, udesale
Target Milestone: z2Keywords: Triaged, ZStream
Target Release: 15.0 (Stein)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tempest-21.0.0-0.20191209200452.702b21c.el8ost Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: 1737757 Environment:
Last Closed: 2020-03-05 12:02:11 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1716594, 1722154, 1737754, 1737757    
Bug Blocks:    

Description Martin Kopec 2019-08-06 07:41:06 UTC
+++ This bug was initially created as a clone of Bug #1737757 +++

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

Description of problem:
When subnetpool extension is not enabled 'tempest cleanup --init-saved-state' exits with a non-zero return code although saved_state.json file is generated properly. 

Version-Release number of selected component (if applicable):
openstack-tempest-18.0.0-9.el7ost

Additional info:
BZ https://bugzilla.redhat.com/show_bug.cgi?id=1722154 is fixed only partially, see https://bugs.launchpad.net/tempest/+bug/1832566/comments/4 and later comments.

Comment 11 Martin Kopec 2019-12-18 14:51:34 UTC
The Fixed in version package contains a fix for the mentioned issue. The exception is handled appropriately now. Moving to VERIFIED.

Comment 13 errata-xmlrpc 2020-03-05 12:02:11 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:0710