Bug 1667834 - OCS 3.11 Deployment Guide: Add a note to set openshift_storage_glusterfs_block_deploy=false when deploying two cluster
Summary: OCS 3.11 Deployment Guide: Add a note to set openshift_storage_glusterfs_bloc...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: doc-Container_Native_Storage_with_OpenShift
Version: ocs-3.11
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
: OCS 3.11.z Batch Update 4
Assignee: Anjana KD
QA Contact: Rachael
URL: https://access.redhat.com/documentati...
Whiteboard:
Depends On:
Blocks: 1709460
TreeView+ depends on / blocked
 
Reported: 2019-01-21 09:22 UTC by Patric Uebele
Modified: 2019-11-04 15:44 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-04 15:44:50 UTC
Embargoed:

Attachments (Terms of Use)

Description Patric Uebele 2019-01-21 09:22:02 UTC 
User-Agent:       Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36
Build Identifier: 

In sections 4.5 step 1 and 5.4 step 1, right under the provided inventory file examples , please add a note:

"It's important to set openshift_storage_glusterfs_block_deploy=false in this deployment scenario"

Overlooking this setting caused significant installation delays recently at MoJ France.

Links to the respective sections in the deployment guide:

https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/3.11/html-single/deployment_guide/#chap-Documentation-Red_Hat_Gluster_Storage_Container_Native_with_OpenShift_Platform-reg_log_met 

https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/3.11/html-single/deployment_guide/#chap-Documentation-Red_Hat_Gluster_Storage_Container_Native_with_OpenShift_Platform-crs_reg_log_met

Reproducible: Always




See https://bugzilla.redhat.com/show_bug.cgi?id=1664365#c5
Note You need to log in before you can comment on or make changes to this bug.