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.