Bug 1657740 - [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
Summary: [DDF] Suggest to add instructions that if the initial overcloud creation fail...
Keywords:
Status: ASSIGNED
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: 13.0 (Queens)
Hardware: All
OS: All
low
high
Target Milestone: ---
: ---
Assignee: Dan Macpherson
QA Contact: RHOS Documentation Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-10 11:04 UTC by Direct Docs Feedback
Modified: 2020-02-04 05:04 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Director 13
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)

Description Direct Docs Feedback 2018-12-10 11:04:00 UTC
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

https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html/director_installation_and_usage/chap-troubleshooting_director_issues#annotations:c41dfc45-b1bf-4226-a311-63f8b6ad9bd9

Comment 1 Nadav Halevy 2019-02-27 13:54:54 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.

Comment 2 Dan Macpherson 2019-05-01 13:32:30 UTC
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.


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