Red Hat Bugzilla – Bug 1313497
Enabling Gluster Service post-facto on HE does not update brick info
Last modified: 2016-12-15 05:16:28 EST
Description of problem:
I had deployed Hosted Engine via the OVF image in package "ovirt-engine-appliance" on my hyperconverged setup (2 virt hosts, also servicing bricks for the two Gluster volumes used for hosted_storage and vm_storage storage domains.) I found out some time after deployment that the Gluster volume management integration isn't enabled by default in this OVF image. So based on a mailing list thread response (http://lists.ovirt.org/pipermail/users/2016-March/038188.html) I executed the needful SQL update statement that enabled the Gluster integration in the UI. After restarting the "ovirt-engine" service in the HE host, I could then see the Gluster volume nodes in the UI, and browse to them for info/management purposes, but noticed that the "Number of Bricks" attribute was reading "0", and nothing was showing in the "Bricks" tab.
Based on a following mailing list thread response, setting each host to "Maintenance" and then activating them again worked to update the Gluster bricks on a per-host basis, and when I had done this process to all hosts in my setup, I now see a true and correct list of bricks per volume.
Version-Release number of selected component (if applicable):
Do an automatic install for HE from the OVF, then subsequently update the Postgres table "vdc_options" setting the value of ApplicationMode to '255'
Steps to Reproduce:
The Gluster Volume info showed up, but the number of bricks per volume was showing as "0"
Had to go thru oVirt hosts one by one, and put into Maintenance mode, then Activate, to get brick info to show in UI
When Gluster Service is enabled post-facto, not only the Volume info is populated, but also the underlying brick info as well per volume
ERRATA: The line above stating "2 virt hosts, also servicing bricks" should read "3 virt hosts, also servicing bricks"
Re-targeting to 4.0.4 as this bug prevents adding HC hosts to cluster (if gluster service is enabled after the first host is added)
Tested with RHV 18.104.22.168-0.1.el7ev
1. Setup the hosted-engine on one of the hypervisor. ( this host also serves gluster volumes )
2. Once the hosted engine is up, updated the engine-config to enable gluster capability on the cluster.
3. From RHV UI, edit the cluster to check 'gluster' capability.
Once the gluster capability is enabled bricks, volume, peers and other information are updated.