Bug 1398323 - Stack delete does not delete mistral environment & swift container corresponding to the stack
Summary: Stack delete does not delete mistral environment & swift container correspond...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-common
Version: 10.0 (Newton)
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Dougal Matthews
QA Contact: Alexander Chuzhoy
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-24 12:52 UTC by Jaison Raju
Modified: 2021-03-11 14:49 UTC (History)
9 users (show)

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.
Clone Of:
Environment:
Last Closed: 2019-10-24 12:49:23 UTC
Target Upstream Version:


Attachments (Terms of Use)

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 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


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