Bug 1936816 - 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: 13.0 (Queens)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: z16
: 13.0 (Queens)
Assignee: Alex Schultz
QA Contact: David Rosenfeld
URL:
Whiteboard:
Depends On:
Blocks: 1938666
TreeView+ depends on / blocked
 
Reported: 2021-03-09 09:02 UTC by Eduard Barrera
Modified: 2022-08-26 15:32 UTC (History)
10 users (show)

Fixed In Version: openstack-tripleo-common-8.7.1-29.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1938666 (view as bug list)
Environment:
Last Closed: 2021-06-16 10:59:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-1954 0 None None None 2022-08-26 15:32:43 UTC
Red Hat Product Errata RHBA-2021:2385 0 None None None 2021-06-16 11:00:22 UTC

Description Eduard Barrera 2021-03-09 09:02:36 UTC
Description of problem:

Overcloud deploy command fail with the following error:

Starting deployment...                                                                                                                                                               
Started Mistral Workflow tripleo.validations.v1.check_pre_deployment_validations. Execution ID: 98443932-858b-4b36-bb7e-29849327432                                                 
Waiting for messages on queue 'tripleo' with no timeout.                                                                                                                             
'passwords'   

It seems it is caused by information missing in the plan-environment.yaml it only contains:

$ cat plan-environment.yaml 
version: 1.0

name: overcloud
description: >
  Default Deployment plan
template: overcloud.yaml
environments:
  - path: overcloud-resource-registry-puppet.yaml
  - path: environments/docker.yaml
  - path: environments/docker-ha.yaml

nothing else.

AFAIK it should contain much more information, also a "passwords" section.

This KCS[1] says that the workaround for this issue is to
delte de plan, but when we try we get the following error:

2021-02-26 12:35:56.762 2771 ERROR mistral.executors.default_executor [req-a1d6f1e5-e2e9-4c31-b20b-be2d851a51f0 3bf795ead5ae403db92ec20498d7db35 134157a06a0d461bba9d385dc4848a35 - default default] Failed to run action [action_ex_id=None, action_cls='<class 'mistral.actions.action_factory.DeletePlanAction'>', attributes='{}', params='{u'container': u'overcloud'}']
 Cannot delete a plan that has an associated stack.: StackInUseError: Cannot delete a plan that has an associated stack.
2021-02-26 12:35:56.762 2771 ERROR mistral.executors.default_executor Traceback (most recent call last):
2021-02-26 12:35:56.762 2771 ERROR mistral.executors.default_executor   File "/usr/lib/python2.7/site-packages/mistral/executors/default_executor.py", line 114, in run_action
2021-02-26 12:35:56.762 2771 ERROR mistral.executors.default_executor     result = action.run(action_ctx)
2021-02-26 12:35:56.762 2771 ERROR mistral.executors.default_executor   File "/usr/lib/python2.7/site-packages/tripleo_common/actions/plan.py", line 119, in run
2021-02-26 12:35:56.762 2771 ERROR mistral.executors.default_executor     raise exception.StackInUseError(name=self.container)
2021-02-26 12:35:56.762 2771 ERROR mistral.executors.default_executor StackInUseError: Cannot delete a plan that has an associated stack.
2021-02-26 12:35:56.762 2771 ERROR mistral.executors.default_executor


[1] https://access.redhat.com/solutions/3714651

Version-Release number of selected component (if applicable):
OSP13

How reproducible:
every time we execute overcloud deploy


Actual results:
mentioned error

Expected results:
- no error during deployment
- able to delete the plan


What can we do to solve this issue and continue
growing ther environment ?

Comment 1 Alex Schultz 2021-03-09 18:59:20 UTC
Does the end user still have their passwords file backed up somewhere?  If not passwords may get regenerated.  You can manually remove the swift plan but there may be other issues that arise from doing this. Testing in a development environment would be recommended.

$ source ~/stackrc
$ openstack container delete -r <stackname>

Comment 25 David Rosenfeld 2021-04-12 18:43:10 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 31 errata-xmlrpc 2021-06-16 10:59:46 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 13.0 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:2385


Note You need to log in before you can comment on or make changes to this bug.