Bug 1841550 - OCS 4.4: Node replacement for Amazon EC2(LSO) should also be segregated for UPI and IPI based installs
Summary: OCS 4.4: Node replacement for Amazon EC2(LSO) should also be segregated for U...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat OpenShift Container Storage
Classification: Red Hat Storage
Component: documentation
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Olive Lakra
QA Contact: Elad
URL:
Whiteboard:
Depends On:
Blocks: 1850476
TreeView+ depends on / blocked
 
Reported: 2020-05-29 12:46 UTC by Neha Berry
Modified: 2022-04-08 14:30 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1850476 (view as bug list)
Environment:
Last Closed: 2022-04-08 14:30:08 UTC
Embargoed:

Attachments (Terms of Use)

Description Neha Berry 2020-05-29 12:46:55 UTC 
Description of problem (please be detailed as possible and provide log
snippests):
----------------------------------------------------------------------
In OCS 4.4 documentation, there are sections for Node replacement for AWS EC2 (LSO) based clusters. But there is no distinction for UPI and IPI based clusters. Also we need  to segragate based on Pro-active and Reactive Replacement


Current section - 8.3.2. Replacing a failed Amazon EC2 node [1] -- seems to be more in par with AWS UPI


[1]  https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/4.4/html-single/managing_openshift_container_storage/index?lb_target=preview#replacing-a-failed-amazon-ec2-node_rhocs

It would be better to have a segregation of node replacement for AWS EC2 in 4 broad sections(similar to section 8.1)

Replacing an operational Amazon EC2 node on user-provisioned infrastructure
Replacing an operational Amazon EC2 node on installer-provisioned infrastructure
Replacing a failed Amazon EC2 node on user-provisioned infrastructure
Replacing a failed Amazon EC2 node on installer-provisioned infrastructure


Version of all relevant components (if applicable):
----------------------------------------------------------------------
OCS 4.4 documentation
Note You need to log in before you can comment on or make changes to this bug.