Description of problem: https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3.3/html-single/container-native_storage_for_openshift_container_platform/#chap-Documentation-Red_Hat_Gluster_Storage_Container_Native_with_OpenShift_Platform-Upgrade-Gluster_pods Section : 13.3 , Point 12 We should have a higher timeout value to bump up op-version as we had seen that the overall time it takes to complete the command depends on number of volumes configured in the cluster and it can go upto 10 minutes for 1000 volumes. gluster --timeout=600 volume set all cluster.op-version <version number> Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Background to why this request is captured at : https://bugzilla.redhat.com/show_bug.cgi?id=1648210
gluster --timeout=3600 volume set all cluster.op-version <version number> The experiment done with the applied patch was on a 256 GB system and hence timeout= 600 will be a very aggressive number and hence on a 32/64 GB RAM, based on the testing result safer number should be 3600. Please note, if the command can finish well before this period too depending on the h/w.
Hi Atin, The doc you are referring to in the bug description is an old document (CNS 3.3). The appropriate content is now in the OCS 3.11 Deployment Guide (section 6.1.3 step 15) - https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/3.11/html-single/deployment_guide/?lb_target=preview#chap-Documentation-Red_Hat_Gluster_Storage_Container_Native_with_OpenShift_Platform-Upgrade-Gluster_pods As per this bug, you have mentioned that the gluster --timeout must be changed from 600 to 3600 while checking the RHGS op-version. However, I do not see any explicit mention of this in the guide. Do you want us to update the following command to include the timeout value: # gluster vol get all cluster.op-version -Chandrakanth
Please check step 15 again. <snip> 15. Check the Red Hat Gluster Storage op-version by executing the following command on one of the gluster pods. # gluster vol get all cluster.op-version Set the cluster.op-version to 31304 on any one of the pods: Note Ensure all the gluster pods are updated before changing the cluster.op-version. # gluster volume set all cluster.op-version 31304 ====> should be changed to gluster --timeout=3600 volume set all cluster.op-version 31304 </snip>
Verified in the link provided at Comment 6 and i see that the changes are present. gluster --timeout=3600 volume set all cluster.op-version 31304 Moving the bug to verified state.