Bug 1737754

Summary: Wrong return code of tempest cleanup
Product: Red Hat OpenStack Reporter: Martin Kopec <mkopec>
Component: openstack-tempestAssignee: Lukas Piwowarski <lpiwowar>
Status: CLOSED ERRATA QA Contact: Lukas Piwowarski <lpiwowar>
Severity: high Docs Contact:
Priority: high    
Version: 13.0 (Queens)CC: apevec, lhh, slinaber, udesale, whayutin
Target Milestone: z8Keywords: Triaged, ZStream
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tempest-18.0.0-10.el7ost Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 1737757 (view as bug list) Environment:
Last Closed: 2019-09-03 16:58:11 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:
Bug Depends On: 1716594    
Bug Blocks: 1737757, 1737759    
Attachments:
Description Flags
test_fix.log none

Description Martin Kopec 2019-08-06 07:29:06 UTC 
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=1716594 is fixed only partially, see https://bugs.launchpad.net/tempest/+bug/1832566/comments/4 and later comments.
Comment 6 Lukas Piwowarski 2019-08-21 15:12:17 UTC 
Created attachment 1606597 [details]
test_fix.log

Tested with:
  - package with the fix (openstack-tempest-18.0.0-10.el7ost)

The bug was reproduced by applying a reverse patch to code from package with the fix. This was done in such a way because the package contains a fix which causes this bug. 

When tested with a patch which should fix the issue the bug was not reproduced. Therefore changing the status to VERIFIED.
Comment 8 errata-xmlrpc 2019-09-03 16:58: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-2019:2623