Bug 1062197
Summary: | dist-geo-rep : glusterfs rolling upgrade (2.1 to 2.1.2) while geo-rep is running results in failure to update stime on bricks. | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Vijaykumar Koppad <vkoppad> |
Component: | geo-replication | Assignee: | Venky Shankar <vshankar> |
Status: | CLOSED ERRATA | QA Contact: | Sudhir D <sdharane> |
Severity: | high | Docs Contact: | |
Priority: | urgent | ||
Version: | 2.1 | CC: | aavati, avishwan, bbandari, csaba, grajaiya, nlevinki, nsathyan, psriniva, vbhat |
Target Milestone: | --- | Keywords: | ZStream |
Target Release: | RHGS 2.1.4 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.4.0.65rhs-1 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-09-18 18:23:22 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: |
Description
Vijaykumar Koppad
2014-02-06 12:44:35 UTC
This bug is valid only when you are upgrading from "2.1 to 2.1.1" or "2.1 to 2.1.2", and documentation to avoid the problem is provided here https://access.redhat.com/site/documentation/en-US/Red_Hat_Storage/2.1/html-single/Installation_Guide/ I'm not even sure that the bug is valid for update 4 (because the bug summary clearly mentions earlier releases) But the upgrade from glusterfs-59rhs to glusterfs-65rhs works just fine. Following are the steps I performed. Steps to upgrade. ============================================ ps -aef | grep gsync | grep -v grep | awk '{print $2}' | xargs kill -9 pkill glusterfs pkill glusterfsd pkill glusterd yum update -y reboot The order of nodes in which above steps should be executed. ============================================================= * Identify a slave node and upgrade it to newr version * Identify a correspnding master and upgrade it. The correspnding master can be identified by ruuning geo-rep status command. * Repeat first 2 steps till all the slave and corresponding master nodes are upgraded. Since above steps are working I am moving the the bug to verified. Please reopen if this does not work. Hi Aravinda, Can you please requires doc text field to "-" if you think this bug does not need to be documented in the errata? Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2014-1263.html |