Bug 1706832

Summary: [upgrade playbook] Document default timeout value set for OCS upgrade playbook volume heal check
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Ashmitha Ambastha <asambast>
Component: doc-Container_Native_Storage_with_OpenShiftAssignee: Amrita <asakthiv>
Status: CLOSED NOTABUG QA Contact: Ashmitha Ambastha <asambast>
Severity: high Docs Contact:
Priority: unspecified    
Version: ocs-3.11CC: asakthiv, asriram, rhs-bugs, storage-doc
Target Milestone: ---Keywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-18 15:15:05 UTC 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: 1703695    
Bug Blocks:    

Description Ashmitha Ambastha 2019-05-06 11:21:33 UTC 
Description of problem:
While the upgrade playbook runs, while upgrading from one gluster pod to another, the volume heal needs to be completed before upgrading the next gluster pod. The default value set for the number of retries while the playbook waits for volume heal to complete is 1200. 

openshift_storage_glusterfs_health_timeout: 1200

This value can be updated with respect number of the volumes on the cluster and help in making the playbook pass at once and not timeout waiting for volume heals to complete. 

Version-Release number of selected component (if applicable): OCS 3.11

How reproducible: Always

Steps to Reproduce:
1. Edit the inventory file and add openshift_storage_glusterfs_health_timeout: 1200 
2. Run the upgrade playbook, 
# ansible-playbook -i <inv_file> /usr/share/ansible/openshift-ansible/playbooks/openshift-glusterfs/upgrade.yml 
3. Playbook should pass and not timeout waiting for vol heals to complete.