Bug 1861069

Summary:	OCS 4.5 : Verifying OCS Deployment - the POD list needs some changes
Product:	[Red Hat Storage] Red Hat OpenShift Container Storage	Reporter:	Neha Berry <nberry>
Component:	documentation	Assignee:	Olive Lakra <olakra>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Neha Berry <nberry>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.5	CC:	asriram, ocs-bugs, olakra
Target Milestone:	---
Target Release:	OCS 4.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1861076 (view as bug list)		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1826397, 1861076, 1861314, 1861316

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: