Description of problem: For HC install, where gluster is enabled - the default cluster in engine does not have gluster service enabled. This is in the ansible based deployment Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: Setup Hosted Engine with GLuster and continue to hosted-engine deployment Actual results: Expected results:
Tested with ovirt-hosted-engine-setup-2.2.16-1 and ansible-2.5.0-1.el7ae.noarch. After hosted-engine deployment, from the RHV UI, I could still see that only virt capability is enabled on the cluster, but not the gluster capability. @Simone, could you help on this issue ?
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Gluster service will be enabled at cluster level if ENABLE_HC_GLUSTER_SERVICE is set: https://github.com/oVirt/ovirt-hosted-engine-setup/blob/master/src/ansible/bootstrap_local_vm.yml#L289 From CLI it works as expected, we need to understand if the cockpit wizard correctly passes it.
In the console logs from cockpit wizard I see: "Gluster values successfully added." and indeed the configuration of my volume comes from there but ENABLE_HC_GLUSTER_SERVICE is not set. By the way ENABLE_HC_GLUSTER_SERVICE is neither in the answer file generated by gdeploy [root@c74he20180302h1 ~]# cat /var/lib/ovirt-hosted-engine-setup/answers/he-answer.conf [environment:default] OVEHOSTED_STORAGE/storageDomainConnection=str:c74he20180302h1.localdomain:/engine OVEHOSTED_STORAGE/mntOptions=str:backup-volfile-servers=c74he20180302h2.localdomain:c74he20180302h3.localdomain
Gobinda, can you add ENABLE_HC_GLUSTER_SERVICE to the he-answers file generated by gdeploy?
Phillip, In the latest cockpit-ovirt-0.11.23-1 ,i still see no gluster service enabled. Component version: gdeploy-2.0.2-26.el7rhgs.noarch cockpit-ovirt-dashboard-0.11.23-1.el7ev.noarch
(In reply to bipin from comment #6) > Phillip, > > In the latest cockpit-ovirt-0.11.23-1 ,i still see no gluster service > enabled. Bipin, Could you please try to reproduce? The flag is passed correctly in all my tests and I'm showing that the service is enabled in the engine when it's supposed to be.
(In reply to Phillip Bailey from comment #7) > (In reply to bipin from comment #6) > > Phillip, > > > > In the latest cockpit-ovirt-0.11.23-1 ,i still see no gluster service > > enabled. > > Bipin, > > Could you please try to reproduce? The flag is passed correctly in all my > tests and I'm showing that the service is enabled in the engine when it's > supposed to be. Hi Philip, I have again retested with RHV 4.2.3 and cockpit-ovirt-dashboard-0.11.24 Again gluster service is not turned on by default on the cluster. What logs do you need ? We did installation on 3 systems, and all the machines have the same problem. I could also provide you the live setup for investigation
(In reply to SATHEESARAN from comment #8) > What logs do you need ? We did installation on 3 systems, and all the > machines have the same problem. I could also provide you the live setup for > investigation Hi Satheesaran, Could you please post the ovirt-hosted-engine-setup-ansible-bootstrap_local_vm-* log from /var/log/ovirt-hosted-engine-setup? I'd like to see what's being passed in the var file. I can decide from there whether access to the test environment will be helpful. Thank you!
Philip, Have attached the log. Could see the below in the logs: ovirt-hosted-engine-setup-ansible-bootstrap_local_vm-20180509112008-ymv7it.log:2018-05-09 11:25:30,572+0530 INFO ansible task start {'status': 'OK', 'ansible_task': u'Enable GlusterFS at cluster level', 'ansible_playbook': u'/usr/share/ovirt-hosted-engine-setup/ansible/bootstrap_local_vm.yml', 'ansible_type': 'task'} ovirt-hosted-engine-setup-ansible-bootstrap_local_vm-20180509112008-ymv7it.log:2018-05-09 11:25:30,572+0530 DEBUG ansible on_any args TASK: Enable GlusterFS at cluster level kwargs is_conditional:False ovirt-hosted-engine-setup-ansible-bootstrap_local_vm-20180509112008-ymv7it.log:2018-05-09 11:25:31,060+0530 INFO ansible skipped {'status': 'SKIPPED', 'ansible_task': u'Enable GlusterFS at cluster level', 'ansible_host': u'localhost', 'ansible_playbook': u'/usr/share/ovirt-hosted-engine-setup/ansible/bootstrap_local_vm.yml', 'ansible_type': 'task'}
I tested the current build on the provided test environment and it worked as expected. I disabled and stopped glusterd on the host before installation. Installation was successful. The glusterd service was both enabled and running after installation completed. Pertinent lines from the logs are below. Could you please check the results on grafton10 and let me know if you have any questions and how you'd like to proceed? /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-ansible-bootstrap_local_vm-2018410154458-1fzj3y.log 2018-05-11 01:14:59,257+0530 DEBUG var changed: host "localhost" var "ENABLE_HC_GLUSTER_SERVICE" type "<type 'bool'>" value: "True" 2018-05-11 01:19:19,922+0530 INFO ansible task start {'status': 'OK', 'ansible_task': u'Enable GlusterFS at cluster level', 'ansible_playbook': u'/usr/share/ovirt-hosted-engine-setup/ansible/bootstrap_local_vm.yml', 'ansible_type':'task'} 2018-05-11 01:19:19,922+0530 DEBUG ansible on_any args TASK: Enable GlusterFS at cluster level kwargs is_conditional:False 2018-05-11 01:19:21,472+0530 INFO ansible ok {'status': 'OK', 'ansible_task': u'Enable GlusterFS at cluster level', 'ansible_host': u'localhost', 'ansible_playbook':u'/usr/share/ovirt-hosted-engine-setup/ansible/bootstrap_local_vm.yml', 'ansible_type': 'task'} ------------ /var/log/ovirt-engine/host-deploy/ovirt-host-deploy-20180511011949-test.example.com-5b2a47da.log 2018-05-11 01:19:27,144+0530 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:204 DIALOG:SEND ***Q:STRING CUSTOMIZATION_COMMAND 2018-05-11 01:19:27,144+0530 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:204 DIALOG:SEND **%QEnd: CUSTOMIZATION_COMMAND 2018-05-11 01:19:27,146+0530 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:204 DIALOG:RECEIVE env-query -k GLUSTER/enable 2018-05-11 01:19:27,146+0530 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:204 DIALOG:SEND **%QStart: GLUSTER/enable 2018-05-11 01:19:27,147+0530 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:204 DIALOG:SEND ### 2018-05-11 01:19:27,147+0530 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:204 DIALOG:SEND ### Please specify value for 'GLUSTER/enable': 2018-05-11 01:19:27,147+0530 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:204 DIALOG:SEND ### Response is VALUE GLUSTER/enable=type:value or ABORT GLUSTER/enable 2018-05-11 01:19:27,147+0530 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:204 DIALOG:SEND ***Q:VALUE GLUSTER/enable 2018-05-11 01:19:27,147+0530 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:204 DIALOG:SEND **%QEnd: GLUSTER/enable 2018-05-11 01:19:27,148+0530 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:204 DIALOG:RECEIVE VALUE GLUSTER/enable=bool:true
(In reply to Phillip Bailey from comment #12) > I tested the current build on the provided test environment and it worked as > expected. I disabled and stopped glusterd on the host before installation. > Installation was successful. The glusterd service was both enabled and > running after installation completed. Pertinent lines from the logs are > below. > > Could you please check the results on grafton10 and let me know if you have > any questions and how you'd like to proceed? > > /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-ansible- > bootstrap_local_vm-2018410154458-1fzj3y.log > > 2018-05-11 01:14:59,257+0530 DEBUG var changed: host "localhost" var > "ENABLE_HC_GLUSTER_SERVICE" type "<type 'bool'>" value: "True" > > 2018-05-11 01:19:19,922+0530 INFO ansible task start {'status': 'OK', > 'ansible_task': u'Enable GlusterFS at cluster level', 'ansible_playbook': > u'/usr/share/ovirt-hosted-engine-setup/ansible/bootstrap_local_vm.yml', > 'ansible_type':'task'} > 2018-05-11 01:19:19,922+0530 DEBUG ansible on_any args TASK: Enable > GlusterFS at cluster level kwargs is_conditional:False > 2018-05-11 01:19:21,472+0530 INFO ansible ok {'status': 'OK', > 'ansible_task': u'Enable GlusterFS at cluster level', 'ansible_host': > u'localhost', > 'ansible_playbook':u'/usr/share/ovirt-hosted-engine-setup/ansible/ > bootstrap_local_vm.yml', 'ansible_type': 'task'} > > ------------ > > /var/log/ovirt-engine/host-deploy/ovirt-host-deploy-20180511011949-test. > example.com-5b2a47da.log > > 2018-05-11 01:19:27,144+0530 DEBUG otopi.plugins.otopi.dialog.machine > dialog.__logString:204 DIALOG:SEND ***Q:STRING CUSTOMIZATION_COMMAND > 2018-05-11 01:19:27,144+0530 DEBUG otopi.plugins.otopi.dialog.machine > dialog.__logString:204 DIALOG:SEND **%QEnd: CUSTOMIZATION_COMMAND > 2018-05-11 01:19:27,146+0530 DEBUG otopi.plugins.otopi.dialog.machine > dialog.__logString:204 DIALOG:RECEIVE env-query -k GLUSTER/enable > 2018-05-11 01:19:27,146+0530 DEBUG otopi.plugins.otopi.dialog.machine > dialog.__logString:204 DIALOG:SEND **%QStart: GLUSTER/enable > 2018-05-11 01:19:27,147+0530 DEBUG otopi.plugins.otopi.dialog.machine > dialog.__logString:204 DIALOG:SEND ### > 2018-05-11 01:19:27,147+0530 DEBUG otopi.plugins.otopi.dialog.machine > dialog.__logString:204 DIALOG:SEND ### Please specify value for > 'GLUSTER/enable': > 2018-05-11 01:19:27,147+0530 DEBUG otopi.plugins.otopi.dialog.machine > dialog.__logString:204 DIALOG:SEND ### Response is VALUE > GLUSTER/enable=type:value or ABORT GLUSTER/enable > 2018-05-11 01:19:27,147+0530 DEBUG otopi.plugins.otopi.dialog.machine > dialog.__logString:204 DIALOG:SEND ***Q:VALUE GLUSTER/enable > 2018-05-11 01:19:27,147+0530 DEBUG otopi.plugins.otopi.dialog.machine > dialog.__logString:204 DIALOG:SEND **%QEnd: GLUSTER/enable > 2018-05-11 01:19:27,148+0530 DEBUG otopi.plugins.otopi.dialog.machine > dialog.__logString:204 DIALOG:RECEIVE VALUE GLUSTER/enable=bool:true Phillip, I think you have mistaken it for gluster service at the systemd level. The issue is related to the 'gluster' service not enabled on the gluster. When you create or edit the cluster from RHV Manager UI, you can see that there are 2 checkboxed one for virt service, and other gluster service. For hyperconverged setup both of these needs to enabled. But currently we do see that only virt service is enabled on the cluster Let me past the screenshot post this comment. Hope that clarifies
Created attachment 1434919 [details] Edit cluster tab Screenshot of cluster, while editing
(In reply to SATHEESARAN from comment #13) > > 2018-05-11 01:19:27,148+0530 DEBUG otopi.plugins.otopi.dialog.machine > > dialog.__logString:204 DIALOG:RECEIVE VALUE GLUSTER/enable=bool:true > > Phillip, > > I think you have mistaken it for gluster service at the systemd level. > > The issue is related to the 'gluster' service not enabled on the gluster. > When you create or edit the cluster from RHV Manager UI, you can see that > there are 2 checkboxed one for virt service, and other gluster service. For > hyperconverged setup both of these needs to enabled. But currently we do see > that only virt service is enabled on the cluster > > Let me past the screenshot post this comment. Hope that clarifies Philip pointed out host-deploy logs and the engine is going to enable and configure the gluster service on the host only if the gluster server is enabled at cluster level.
(In reply to Simone Tiraboschi from comment #15) > Philip pointed out host-deploy logs and the engine is going to enable and > configure the gluster service on the host only if the gluster server is > enabled at cluster level. So in the hyperconverged cases, the cluster should have got the 'gluster' service enabled, before the addition of first host ( HE host ) to this cluster. Currently this is not happening.
Looks like with the latest RHVH build - rhvh-4.2.3.0-0.20180508.0+1 - I observe that the gluster service is enabled on the cluster by default. The infra was used earlier and the test failed as commented in comment8 Not sure why. I repeated this test multiple times with latest RHVH and finding the gluster service is always enabled on the cluster. Phillip, Could this bug be moved ON_QA for verification ?
(In reply to SATHEESARAN from comment #17) > Phillip, Could this bug be moved ON_QA for verification ? Simone got to it before me, but I concur with it being moved to ON_QA.
Tested with RHV-4.2.3-5 and glusterfs-3.12 with ovirt-hosted-engine-setup-2.2.20-1.el7ev.noarch gluster service is enabled in the 'Default' cluster along with 'virt' service
This bugzilla is included in oVirt 4.2.3 release, published on May 4th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.3 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.