Bug 1657740
Summary: | [DDF] Suggest to add instructions that if the initial overcloud creation fails, that the user should run the command "openstack stack delete overcloud" before attempting again | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Direct Docs Feedback <ddf-bot> |
Component: | documentation | Assignee: | Dan Macpherson <dmacpher> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | RHOS Documentation Team <rhos-docs> |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | 13.0 (Queens) | CC: | dmacpher |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: |
Director 13
|
|
Last Closed: | 2021-08-31 06:44:49 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Direct Docs Feedback
2018-12-10 11:04:00 UTC
openstack stack delete overcloud --yes --wait Suggest also to mention that if you run the above command you can see the progress instead of having to repeatedly run 'openstack stack list' to see if it has completed. There's legitimacy to this BZ. However, the only thing to be aware of is that customers who have created their overcloud and are updating with "openstack overcloud deploy" might run into a failure and think they have to run "openstack overcloud delete", which they shouldn't do because it'll delete their running overcloud. Might require a note to specify this information. Also added to the troubleshooting section |