Bug 1666931
| Summary: | Removed networks after the tempest cleanup | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Robin Cernin <rcernin> | ||||
| Component: | openstack-tempest | Assignee: | Chandan Kumar <chkumar> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Martin Kopec <mkopec> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 13.0 (Queens) | CC: | apevec, bshephar, lhh, mkopec, slinaber, udesale | ||||
| Target Milestone: | z6 | Keywords: | Triaged, ZStream | ||||
| Target Release: | 13.0 (Queens) | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | openstack-tempest-18.0.0-7.el7ost | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | |||||||
| : | 1673103 (view as bug list) | Environment: | |||||
| Last Closed: | 2019-04-30 17:23:43 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: | 1673103 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
|
Description
Robin Cernin
2019-01-17 01:09:44 UTC
Created attachment 1554559 [details]
verification output
The package (openstack-tempest-18.0.0-7.el7ost) is present in the RHOS 13 repository (also via latest symlink).
I attached an output where can be seen that if the new version of openstack-tempest (openstack-tempest-18.0.0-7.el7ost) is installed the origin networks are not deleted after tempest cleanup -> marking the BZ as VERIFIED.
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:0926 |