Description of problem: ----------------------- The gluster cluster as we know as 'Trusted Storage Pool' has 2 nodes running RHGS 2.1. The nodes have replica 2 volumes These 2 nodes were upgraded to RHGS 3.1 using 'in-service software upgrade' procedure. Upgrade was successful. When the new RHGS 3.1 node installed through ISO, was probed from the already existing cluster, this new node was 'rejected' To summarize, new RHGS 3.1 nodes couldn't be added to the cluster which was upgraded from RHGS 2.1 to RHGS 3.1 Version-Release number of selected component (if applicable): ------------------------------------------------------------- RHGS 2.1 Update6 ( glusterfs-3.4.0.72-1.el6rhs ) RHGS 3.1 ( glusterfs-3.7.1-11.el6rhs ) How reproducible: ----------------- Always Steps to Reproduce: ------------------- 1. Install 2 servers with RHGS 2.1 2. After successful installation create a gluster cluster 'Trusted Storage Pool' 3. Create a replica volume and start it 4. Perform 'in-service software upgrade' from RHGS 2.1 to RHGS 3.1 5. After both the nodes are upgraded, probe( add ) a new RHGS 3.1 node (installed through ISO ) Actual results: --------------- Newly probed node goes to ** rejected ** state Expected results: ----------------- New probe should added as a part of the upgraded cluster
Created attachment 1057933 [details] sosreport from dhcp37-51
Created attachment 1057937 [details] sosreport from dhcp37-142
Upstream patch: http://review.gluster.org/#/c/12171/
Downstream patch: https://code.engineering.redhat.com/gerrit/#/c/60332/
Verified this bug with latest version of 3.1.2 (glusterfs-3.7.5-5). Issue still remains same. Based on discussion with Anand, came to know the dependecy bug which need to be fixed to verify this bug - https://bugzilla.redhat.com/show_bug.cgi?id=1276541 So verification of this bug will be in wait state untill above mentioned bug get addressed.
Still i am seeing the original issue with latest rhgs version ( glusterfs-3.7.5-6 ) that is, after upgrading the 2.1.6 cluster to 3.1.2, peer status after peer probing a new 3.1.2 node is showing "Rejected" This bug depends on https://bugzilla.redhat.com/show_bug.cgi?id=1283035 Currently verification of this bug is blocked with the available rhgs version ***glusterfs-3.7.5-6***
Byreddy Bump-up op-version is required after upgrade all nodes. Could you re-test this by this.
Verified based on Anand comment, that is by bumping up the op-version , every thing worked well with RHGS version...glusterfs-3.7.5-6 Moving to verified state.
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://rhn.redhat.com/errata/RHBA-2016-0193.html