Bug 1765555

Summary:	peers went into rejected state, after upgrade from 3.3.1 to 3.5.0
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Bala Konda Reddy M <bmekala>
Component:	glusterd	Assignee:	Sanju <srakonde>
Status:	CLOSED ERRATA	QA Contact:	Bala Konda Reddy M <bmekala>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	rhgs-3.5	CC:	amukherj, rhs-bugs, rkothiya, storage-qa-internal, vbellur, vdas
Target Milestone:	---
Target Release:	RHGS 3.5.0
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-6.0-21	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-30 12:23:03 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:
Bug Blocks:	1696809

Description Bala Konda Reddy M 2019-10-25 12:05:14 UTC

Description of problem:
On 6 node cluster create all types of volumes, distribute, replicate, arbiter, disperse, distribute-replicate, distribute-disperse, start them and mount.
Stop distribute volume. 
Perform in-service upgrade by stoping all gluster processes in the first node N1
After upgrade few nodes are in Peer rejected state.


Version-Release number of selected component (if applicable):
Upgrade from glusterfs-3.8.4-54.15.el7rhgs.x86_64 to 
glusterfs-6.0-20.el7rhgs.x86_64

How reproducible:
1/1

Steps to Reproduce:
1. Form cluster with 6 nodes
2. Create all types volumes and start them
3. Mount all the volumes on two clients and start IO 
4. Stop distribute volume
5. Perform in-service upgrade on the first node say N1
   systemctl stop glusterd;
   pkill glusterfsd
   pkill glusterfs


Actual results:
After upgrade performed reboot and peers are in rejected state

Expected results:
After performing reboot after upgrade, peers should be in connected state. 

Additional info:

Comment 10 errata-xmlrpc 2019-10-30 12:23:03 UTC

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.

https://access.redhat.com/errata/RHEA-2019:3249