Bug 1398323

Summary:	Stack delete does not delete mistral environment & swift container corresponding to the stack
Product:	Red Hat OpenStack	Reporter:	Jaison Raju <jraju>
Component:	openstack-tripleo-common	Assignee:	Dougal Matthews <dmatthew>
Status:	CLOSED NOTABUG	QA Contact:	Alexander Chuzhoy <sasha>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	10.0 (Newton)	CC:	aschultz, beth.white, jbuchta, jraju, jschluet, mburns, mzheng, rbrady, slinaber
Target Milestone:	---	Keywords:	Documentation, Triaged, ZStream
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Known Issue
Doc Text:	The 'stack delete' command does not delete the mistral environment and swift container corresponding to the deleted stack. Use "openstack overcloud plan delete" after deleting a stack.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-24 12:49:23 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:

Description Jaison Raju 2016-11-24 12:52:15 UTC

Description of problem:
Stack delete does not delete mistral environment & swift container corresponding to the stack .
This causes subsequent stack create to use some environment files used previously in the new stack create , even though those file are not included any more for stack creation via director .

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

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
I guess the patch is already available .

Comment 1 Jaison Raju 2016-11-24 12:52:30 UTC

https://review.openstack.org/gitweb?p=openstack/tripleo-common.git;a=commitdiff;h=ca2bd11d6141f1fbafca888a8e402f043a620bb1

Comment 3 Dougal Matthews 2016-11-24 12:56:04 UTC

The patch linked doesn't delete the plan automatically. There is a CLI command that can delete it; "openstack overcloud plan delete" - this has been available for some time.

Subsequent deploys should not re-use environment files from the previous deploy. If that is happening, this is the real bug and it should be resolved.

Comment 4 Jaison Raju 2016-12-06 05:28:00 UTC

(In reply to Dougal Matthews from comment #3)
> Subsequent deploys should not re-use environment files from the previous
> deploy. If that is happening, this is the real bug and it should be resolved.

Hi Dougal ,

This is noticed on osp10-puddle-2016-11-10.3 .
For example:

i. Deploy a stack with /home/stack/vault/jaison/templates/vlan-provider_ceph/inject-trust-anchor-hiera.yaml
with following content .
parameter_defaults:
  CAMap:
    CA1:
      content: |
        -----BEGIN CERTIFICATE-----
.....
    CA2:
      content: |
        -----BEGIN CERTIFICATE-----

ii. This can be confirmed from overcloud nodes from overcloud nodes in /etc/puppet/hieradata/service_configs.yaml :
tripleo::trusted_cas::ca_map: {
  "CA1": {
    "content": "-----BEGIN CERTIFICATE-----\

iii. Delete stack .

iv. Deploy stack without the above file '/home/stack/vault/jaison/templates/vlan-provider_ceph/inject-trust-anchor-hiera.yaml' .

v. It is still noticed that tripleo::trusted_cas::ca_map: is set with original value .

vi. If we delete swift object & mistral environment , this issue is not seen .

Regards,
Jaison R

Comment 5 Ryan Brady 2017-08-30 14:28:41 UTC

Docs issue, workaround added in doctext