Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1664602

Summary: The overcloud delete should not delete the plan
Product: Red Hat OpenStack Reporter: Udi Kalifon <ukalifon>
Component: python-tripleoclientAssignee: Adriano Petrich <apetrich>
Status: CLOSED WONTFIX QA Contact: Gurenko Alex <agurenko>
Severity: high Docs Contact:
Priority: medium    
Version: 14.0 (Rocky)CC: aschultz, hbrock, jbuchta, jslagle, mburns, rdopiera
Target Milestone: ---Keywords: Triaged, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-24 21:26:52 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:

Description Udi Kalifon 2019-01-09 09:34:12 UTC
Description of problem:
The command "openstack overcloud delete" chains another workflow which deletes the plan in addition to undeploying the overcloud. We want the command to undeploy the overcloud and update the plan status, but not delete the plan entirely.

(undercloud) [stack@undercloud-0 ~]$ openstack overcloud delete yac 
Are you sure you want to delete this overcloud [y/N]? y
Undeploying stack yac...
Waiting for messages on queue 'tripleo' with no timeout.
Deleting plan yac...
None
Success.

See also bug https://bugzilla.redhat.com/show_bug.cgi?id=1644861


Version-Release number of selected component (if applicable):
python-tripleoclient-10.6.1-0.20181010222413.8c8f259.el7ost.noarch


How reproducible:
100%

Steps to Reproduce:
1. Deploy a plan, preferably from the GUI (where you configure the plan and your work is stored in it)
2. Undeploy the overcloud from the CLI: openstack overcloud delete <<plan-name>>


Actual results:
The plan is also deleted. In the GUI you'll have to recreate all your work from scratch.


Expected results:
The CLI workflow should match the GUI's workflow, to undeploy the overcloud and update the plan status - but not delete the plan entirely.