[Bugs] [Bug 1544461] 3.8 -> 3.10 rolling upgrade fails (same for 3.12 or 3.13) on Ubuntu 14

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1544461



--- Comment #10 from Atin Mukherjee <amukherj at redhat.com> ---
(In reply to Marc from comment #9)
> (In reply to Atin Mukherjee from comment #8)
> > Sorry to hear that the suggested work around didn't work :-/
> > 
> > Please try this out:
> > 
> > 1. bring down glusterd instance on 3.8.15 server
> > 
> > 2. from 3.10.10 server remove tier-enabled=0 entry but don't restart
> > glusterd service.
> > 
> > 3. bring up glusterd instance on 3.10.10 server
> > 
> > 4. check 'gluster peer status' and 'gluster volume status' output on both
> > the nodes
> 
> Hi Atin,
> 
> I didn't exactly understand the above steps, are you referring at step (1)
> to stop the 3.10.10 instead of 3.8.15 server? Otherwise (2) step is done
> already (tier-enabled=0 entry removed) and at step (3) ... i never stopped
> the 3.10.10 instance so that i could bring up. The 'gluster peer status'
> will show 'peer rejected( disconnected) if i stop the 3.8.15 server and i
> run the command from 3.10.10.

I am requesting not to stop the glusterd instance running with 3.10.10. Just
take out tier-enabled=0 entry from all the volume info files and then restart
glusterd instance on 3.8.15. Please do let me know if you have any other
confusions.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=gRQv2O4owQ&a=cc_unsubscribe