Sorry for the delay, I've managed to fix it. It was all due to a permission error in the gluster volume which I created via CLI manually, I forgot to set the vdsm unix user UID and GID permissions to it. After doing that, I could import the new gluster volume as a data domain in the new cluster and then enable Gluster management in the cluster and now everything works as expected!

2017-03-23 12:26 GMT+01:00 Sahina Bose <sabose@redhat.com>:

Could you provide engine.log from engine and vdsm.log & supervdsm.log from this host?

On Wed, Mar 22, 2017 at 8:02 PM, Davide Ferrari <davide@billymob.com> wrote:
I get this error when I click "
Gluster status is disconnected for this host.
Restart Glusterd service" in the Genral tab of a the sole host in a new cluster. I've enabled "Manage Gluster" in the cluster options and already created a new gluster volume (via CLI) with bricks only in the hosts that are part of this new cluster.

--
Davide Ferrari
Senior Systems Engineer

_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Davide Ferrari

Senior Systems Engineer