Seems that the "info" command is broken. the status command for example seems to work ok. Matteo ----- Il 17-feb-16, alle 14:15, Sahina Bose sabose@redhat.com ha scritto:
[+gluster-users]
Any known compat issues with gluster 3.7.8-1.el7 client packages and glusterfs 3.7.6-1.el7 server?
On 02/17/2016 04:33 PM, Matteo wrote:
Hi,
today I update one node os, in the updates gluster client packages where upgraded from 3.7.6-1.el7, centos-ovirt36 repository to 3.7.8-1.el7, ovirt-3.6-glusterfs-epel and after reboot the node was marked not operational.
looking into the logs, vdsm was failing to get gluster volume information.
the command (ovirt-storage is the gluster storage where the hosted engine is kept)
gluster --mode=script volume info --remote-host=gluster1 ovirt-storage --xml
was failing, returning error 2 (and no output)
doing yum downgrade on gluster client packages (back to 3.7.6-1.el7, centos-ovirt36) fixed everything.
Data nodes are running glusterfs 3.7.6-1.el7.
The funny thing is that from the ovirt I was able to manually mount the glusterfs shares, only the volume info command was failing, thus breaking vdsm.
Any hint?
regards, Matteo
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users