Bug 2090706 - Ambiguous message in "16.3. Removing Compute nodes" section of Director installation and usage guide
Summary: Ambiguous message in "16.3. Removing Compute nodes" section of Director insta...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: 16.1 (Train)
Hardware: All
OS: All
unspecified
medium
Target Milestone: ---
: ---
Assignee: RHOS Documentation Team
QA Contact: RHOS Documentation Team
URL:
Whiteboard:
Depends On:
Blocks: 2023628
TreeView+ depends on / blocked
 
Reported: 2022-05-26 12:08 UTC by Alex Stupnikov
Modified: 2022-06-22 08:04 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-22 08:04:40 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-15405 0 None None None 2022-05-26 12:18:35 UTC

Description Alex Stupnikov 2022-05-26 12:08:33 UTC 
Description of problem:

In "16.3. Removing Compute nodes" section of Director installation and usage guide we recommend customers to run deployment command if overcloud is in UPDATE_FAILED after scale-in failure when IPMI interface of removed node was not reachable (points 8i and 8ii). But our message looks a bit inconsistent: it is unclear if customer needs to take steps described in point 8i or in both 8i and 8ii if he ended up in this situation.

From my perspective we can re-factor text a bit: move some text from point 8i to point 8 and then recommend to follow both 8i and 8ii.


Version-Release number of selected component (if applicable):
RHOSP 16.1
Comment 13 Irina 2022-06-22 08:04:40 UTC 
Thank you Keigo!

Closing this as NOTABUG because the requested content already exists in our documentation:

https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.2/html-single/director_installation_and_usage/index#proc_removing-or-replacing-a-compute-node_scaling-overcloud-nodes
Note You need to log in before you can comment on or make changes to this bug.