Document URL: https://access.redhat.com/documentation/en-US/Red_Hat_Storage/3.1/html/Installation_Guide/chap-Update.html#Updating_Red_Hat_Storage_in_the_Offline_Mode Section Number and Name: 8.1. Updating Red Hat Gluster Storage from 3.0.x to 3.1.x in the Offline Mode Describe the issue: Offline update has the following mistakes : 1) Step 3 under section 8.1 says "The update process automatically restarts the glusterd management deamon. The glusterfs server processes, glusterfsd is not restarted by default since restarting this daemon affects the active read and write operations. " But as discussed with By Reddy, yum update won't be allowed as long as gluster processes are not killed. 2) Bumping up the op-version is the last thing to be done according to the guide. But op-version should be bumped up first and then volume should be stopped and started. 3) It will be helpful if exact command (with options, if any) to start glusterd after update is mentioned in the guide to avoid any confusion. Suggestions for improvement: Additional information: Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: Document URL: Section Number and Name: Describe the issue: Suggestions for improvement: Additional information: Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: Document URL: Section Number and Name: Describe the issue: Suggestions for improvement: Additional information:
Offline upgrade section doesn't mention to stop the volume before doing an upgrade which technically doesn't qualify it as an offline upgrade. So here are the list of changes I suggest: 1. So in section 8.1, step 3 before mentioning the following mention to stop all the volumes. # service glusterd stop # pkill glusterfs # pkill glusterfsd # yum update 2. In step 6, remove volume stop as the volumes are already stopped as per point 1. Now as per #c6, we have seen an issue in the upgrade path (both offline & in-service) from 3.0.4 to 3.1.x where volfiles are not regenerated and a work around is required here to avoid this issue. post 'yum update' following needs to be done. 1. grep -irns "geo-replication module not working as desired" /var/log/glusterfs/etc-glusterfs-glusterd.vol.log | wc -l If the output is non-zero, then go to step 2 2. Check if glusterd instance is running or not by 'ps aux | grep glusterd', if it is, then stop the glusterd service. 3. glusterd --xlator-option *.upgrade=on -N and then proceed ahead with rest of the steps as per the guide. So to conclude, we'd need to highlight the above work around for 3.0.x to 3.1.x offline/in-service upgrade path and the changes mentioned at the beginning applies for offline upgrade path only.
Hi Laura, Please modify the version 3.0.4 to 3.0.x in the statement "If you're upgrading from 3.0.4 to 3.1.x" because issue is there with 3.0.3 as well so any customer using 3.0.x has to follow the warning steps specified. Modification is needed in both offline and online sections. Moving to assigned state for modifications. Thanks,Byreddy
Changes looks good to me. Moving to verified state.
Closing bugs released as part of 3.1.3 GA and 3.1.3 Async update.