[Bugs] [Bug 1544461] 3.8 -> 3.10 rolling upgrade fails (same for 3.12 or 3.13) on Ubuntu 14
bugzilla at redhat.com
bugzilla at redhat.com
Tue Feb 13 08:19:21 UTC 2018
https://bugzilla.redhat.com/show_bug.cgi?id=1544461
Atin Mukherjee <amukherj at redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |alexandrumarcu at gmail.com
Flags| |needinfo?(alexandrumarcu at gm
| |ail.com)
--- Comment #6 from Atin Mukherjee <amukherj at redhat.com> ---
(In reply to Marc from comment #5)
> Hi Atin,Hari,
>
> I have deleted the "tier-enabled=0" line from the upgraded server but it
> still does not work. If i restart the Gluster service the "info" files it is
> regenerated and the "tier-enabled=0" line is added again.
>
> If i delete and not restart i have the same :
>
> root at 2-gls-dus21-ci-efood-real-de:/var/lib/glusterd/vols/gluster_volume#
> gluster volume status
> Status of volume: gluster_volume
> Gluster process TCP Port RDMA Port Online Pid
> -----------------------------------------------------------------------------
> -
> Brick 2-gls-dus21-ci-efood-real-de.openstac
> klocal:/export_vdb N/A N/A N N/A
> NFS Server on localhost N/A N/A N N/A
>
> Task Status of Volume gluster_volume
> -----------------------------------------------------------------------------
> -
> There are no active volume tasks
>
>
> If i delete and restart, the file gets the line back and the output is:
>
> root at 2-gls-dus21-ci-efood-real-de:/var/lib/glusterd/vols/gluster_volume#
> gluster volume status
> Status of volume: gluster_volume
> Gluster process TCP Port RDMA Port Online Pid
> -----------------------------------------------------------------------------
> -
> Brick 2-gls-dus21-ci-efood-real-de.openstac
> klocal:/export_vdb 49152 0 Y
> 26586
> Self-heal Daemon on localhost N/A N/A Y
> 26568
>
> Task Status of Volume gluster_volume
> -----------------------------------------------------------------------------
> -
> There are no active volume tasks
I see that your brick is up here. What's the output of peer status? If all
peers are in befriended and connected state, we should be good. What's the
difference between the last and the first step what you mentioned?
--
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=4XgTqs2erm&a=cc_unsubscribe
More information about the Bugs
mailing list