Bug 1861069 - OCS 4.5 : Verifying OCS Deployment - the POD list needs some changes
Summary: OCS 4.5 : Verifying OCS Deployment - the POD list needs some changes
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenShift Container Storage
Classification: Red Hat Storage
Component: documentation
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: OCS 4.5.0
Assignee: Olive Lakra
QA Contact: Neha Berry
URL:
Whiteboard:
Depends On:
Blocks: 1826397 1861076 1861314 1861316
TreeView+ depends on / blocked
 
Reported: 2020-07-27 18:09 UTC by Neha Berry
Modified: 2020-09-16 07:43 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1861076 (view as bug list)
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description Neha Berry 2020-07-27 18:09:33 UTC
Description of problem (please be detailed as possible and provide log
snippests):
------------------------------------------

OCS 4.5 Preview link: https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/4.5/html-single/deploying_openshift_container_storage/index?lb_target=preview#verifying-the-state-of-the-pods_aws-vmware

Current chapter
-----------------
4. Verifying OpenShift Container Storage deployment for internal mode

4.1. Verifying the state of the pods

Table 4.1. Pods corresponding to storage components for a three worker node cluster

>> Changes Needed:

1. Change "Mon" to "MON"
2. Replace "rook-ceph-mgr" with "MGR" to be symmetrical with other ceph POD 
Components in the table (MON, MDS)

3. Need to add "RGW" - Count=2 for on-prem clusters(BM/Vsphere).

   Current POD list is from an AWS setup and is missing RGW(deployed only on non-cloud cluters)

Version of all relevant components (if applicable):
------------------------------------------
OCS 4.5


Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?


Is there any workaround available to the best of your knowledge?


Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?


Can this issue reproducible?


Can this issue reproduce from the UI?


If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1.
2.
3.


Actual results:


Expected results:


Additional info:


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