Description of problem: Once user replaces the primary gluster node and if he tries to reinstall any nodes in the cluster /etc/ovirt-hosted-engine/hosted-engine.conf contents are overwritten. I see that value for "storage" is overwritten and host fails to mount the storage and goes to nonoperational. Version-Release number of selected component (if applicable): Red Hat Virtualization Manager Version: 4.1.1.2-0.1.el7 How reproducible: Always Steps to Reproduce: 1. Replace primary gluster server in HC cluster 2. Now try reinstalling any node in the cluster 3. Actual results: I see that /etc/ovirt-hosted-engine/hosted-engine.conf file gets overridden. value of storage points to the old host which is removed and due to this host is not able to mount storage and goes to non operational state. Expected results: /etc/ovirt-hosted-engine/hosted-engine.conf file should not be overwritten when a host is re-installed.
Is there a workaround?
sahina, i moved the node to maintenance changed the contents of /etc/ovirt-hosted-engine.conf file to point to correct storage path, rebooted the node and activated it which brought the node online and mounted all the volumes back.
If user retries Hosted Engine deployment for any reason, /etc/ovirt-hosted-engine/hosted-engine.conf file will not contain the mnt_options. user can later on edit this file to set the mnt_options. But if user tries to reinstall any of the node from UI, mnt_options from the conf file will be lost.
Simone, are we adding UI enhancements to edit the conf file? Should this bug be retargeted?
The engine fetches that value from the initial answerfile stored on a configuration volume on the hosted-engine storage domain. We have an helper utility ('hosted-engine --set-shared-config') to let the user edit values there but currently he can just modify notifications related values.
Is this on track to get into 4.1.5?
(In reply to Yaniv Kaul from comment #6) > Is this on track to get into 4.1.5? No code changes are required here: once 1457357 got it (and we are going to have it in 4.1.5) it's just a matter of documenting how to use it.
Moving this to ON_QA as bug 1457357 is already in.
Thanks sahina!!! We will get this verified for 4.1.8
Moving this back to assigned state as i see that once the primary node is replaced and if user tries to reinstall any other node i see that /etc/ovirt-hosted-engine/hosted-engine.conf gets overwritten to the older value. This time i see that host does not move to non operational instead i see that HA score does not appear and running hosted-engine --vm-status gives the error below. [root@zod ~]# hosted-engine --vm-status Traceback (most recent call last): File "/usr/lib64/python2.7/runpy.py", line 162, in _run_module_as_main "__main__", fname, loader, pkg_name) File "/usr/lib64/python2.7/runpy.py", line 72, in _run_code exec code in run_globals File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_setup/vm_status.py", line 180, in <module> if not status_checker.print_status(): File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_setup/vm_status.py", line 104, in print_status all_host_stats = self._get_all_host_stats() File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_setup/vm_status.py", line 73, in _get_all_host_stats all_host_stats = ha_cli.get_all_host_stats() File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py", line 160, in get_all_host_stats return self.get_all_stats(self.StatModes.HOST) File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py", line 105, in get_all_stats stats = broker.get_stats_from_storage(service) File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py", line 233, in get_stats_from_storage result = self._checked_communicate(request) File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py", line 261, in _checked_communicate .format(message or response)) ovirt_hosted_engine_ha.lib.exceptions.RequestError: Request failed: failed to read metadata: [Errno 107] Transport endpoint is not connected: '/rhev/data-center/mnt/glusterSD/10.70.36.78:_engine/7f8bb254-e645-4152-898a-fe711af9fd53/ha_agent/hosted-engine.metadata'
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.
Moving this back to QA as editing storage domain option should work
Verified and works fine with build ovirt-hosted-engine-setup-2.1.4-1.el7ev.noarch During the replacement of primary node to set the storage path, instead of editing the file /etc/ovirt-hosted-engine/hosted-engine.conf manually there is an option to set it via hosted-engine --set-shared-config and the value can be set as below[1] . When the value is set as shown below it does not get rewritten during reinstall of the host. [1] hosted-engine --set-shared-config storage <ip_of_the_replaced_node>:/engine>