Bug 2033713 - [DDF] [Metro-DR Stretch cluster] - table 4.1 entries "For arbiter" might be misleading
Summary: [DDF] [Metro-DR Stretch cluster] - table 4.1 entries "For arbiter" might be m...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: documentation
Version: 4.9
Hardware: All
OS: All
unspecified
unspecified
Target Milestone: ---
: ODF 4.9.2
Assignee: Olive Lakra
QA Contact: Neha Berry
URL:
Whiteboard:
Depends On:
Blocks: 2048911
TreeView+ depends on / blocked
 
Reported: 2021-12-17 16:56 UTC by Direct Docs Feedback
Modified: 2023-08-09 16:43 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2048911 (view as bug list)
Environment:
Last Closed: 2023-03-09 12:47:11 UTC
Embargoed:


Attachments (Terms of Use)

Description Direct Docs Feedback 2021-12-17 16:56:35 UTC
[Metro-DR Stretch cluster] - table 4.1 entries "For arbiter" might be misleading

Table 4.1 contains descriptions about the pods to check for. Some comments contain "For arbiter,.."  which might be misleading, since it would suggest to check the arbiter node but simply is a relict from previous changes. This should be removed and only state "xx pods ....). 
The whole guide is about metro-DR stretched and thus would not require additional hints like this - nothing else is described here.)

Reported by: matthiasmuench

https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.9/html/configuring_openshift_data_foundation_for_metro-dr_stretch_cluster/verifying-openshift-data-foundation-deployment_rhodf#annotations:077dde5c-693d-4b11-8dd4-2e72bb8730a1


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