Openstack overcloud delete should call the undeploy workflow
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Critical
|
Adriano Petrich |
Bug Description
Description of problem:
I tried to deploy from the GUI with 3 controllers and 1 compute (all other settings were left as default). Deployment failed because the controllers couldn't ping pool.ntp.org (probably a missing DNS setting in the ctlplane) and the GUI showed:
Deployment of plan plan failed
Ansible failed, check log at /var/lib/
The GUI didn't show a "delete" button or any other option - so I deleted the stack from the CLI. However, even with the stack deleted the GUI still showed the same failure and there is no "Deploy" button to try the deployment again.
Version-Release number of selected component (if applicable):
openstack-
How reproducible:
100%
Steps to Reproduce:
1. Deploy from the GUI
2. Delete the stack with "openstack stack delete <<plan-name>>"
3. Return to the GUI
Actual results:
Stack is not shown as deleted, the system doesn't allow you to redeploy.
Possible Solution:
1. Update 'openstack overcloud delete' command to use undeploy_plan workflow instead of 'stack delete'. [1]
2. In cases where documentation mentions using 'openstack stack delete' to delete the deployment, replace it with 'openstack overcloud delete' (to completely delete deployment and plan) or `openstack workflow execution create tripleo.
For the future (not part of this bug) we need to change the 'openstack overcloud delete' to just undeploy plan but not delete it. Deleting plan needs to be separate operation done by 'openstack overcloud plan delete'.
[1] https:/
Fix proposed to branch: master /review. openstack. org/616199
Review: https:/