Bug 1938666 - overcloud plan is corrupted and it can't be deleted to regenerate a new one
Summary: overcloud plan is corrupted and it can't be deleted to regenerate a new one
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-common
Version: 16.1 (Train)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: z6
: 16.1 (Train on RHEL 8.2)
Assignee: Adriano Petrich
QA Contact: David Rosenfeld
URL:
Whiteboard:
Depends On: 1936816
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-15 06:47 UTC by Rabi Mishra
Modified: 2022-08-30 11:48 UTC (History)
13 users (show)

Fixed In Version: openstack-tripleo-common-11.4.1-1.20210315093506.75bd92a.el8ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1936816
Environment:
Last Closed: 2021-05-26 13:51:50 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-1918 0 None None None 2022-08-30 11:48:02 UTC
Red Hat Product Errata RHBA-2021:2097 0 None None None 2021-05-26 13:52:24 UTC

Comment 8 Jad Haj Yahya 2021-04-19 22:32:22 UTC 
Verified using this procedure:

Deployed 3control-2compute toplogy
Recorded the environment using: openstack stack environment show overcloud > plan-environment.yaml
Deleted the plan using: openstack container delete --recursive overcloud
Successfully redeployed the overcloud
Recorded the environment a second time using the same command: openstack stack environment show overcloud > plan-environment.yaml
Compared the two plan-environment.yaml files and no passwords had been modified
Comment 15 errata-xmlrpc 2021-05-26 13:51:50 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 (Red Hat OpenStack Platform 16.1.6 bug fix and enhancement 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-2021:2097
Note You need to log in before you can comment on or make changes to this bug.