[Bugs] [Bug 1672711] Upgrade from glusterfs 3.12 to gluster 4/5 broken

bugzilla at redhat.com bugzilla at redhat.com
Fri Feb 15 13:56:06 UTC 2019


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

Sahina Bose <sabose at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|needinfo?(sabose at redhat.com |needinfo?(kkeithle at redhat.c
                   |)                           |om)
                   |needinfo?(sbonazzo at redhat.c |
                   |om)                         |



--- Comment #5 from Sahina Bose <sabose at redhat.com> ---
(In reply to Kaleb KEITHLEY from comment #4)
> Does removing glusterfs-gnfs manually/explicitly, followed by update, work?

That works, but is not the option that we want to provide users. Since updates
happen from UI, we want this to be as seamless as possible. 
> 
> AFAIK oVirt doesn't use NFS at all and never needed glusterfs-gnfs in the
> first place.

OVirt users who use nfs option to mount gluster, do use glusterfs-gnfs. And we
had a dependency on glusterfs-gnfs to workaround an earlier bug, so this
package is now available on all hosts.

> 
> If glusterfs-gnfs was being used on the same system for something else, it
> should be replaced with a nfs-ganesha deployment, also from the Storage SIG.
> 
> And you can't use an old version of glusterfs-gnfs (e.g. 3.12.x) with
> glusterfs-5.x.
> 
> I will close this as NOTABUG in a few days unless I hear back.


We want the upgrade from 3.12 to > 4 versions to work. So adding Obsoletes in
glusterfs spec as suggested by others - is this a possible option?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list