3. What is the nature and description of the request? When we run the ovirt-engine-rename tool on hosted-engine VM, the configuration of fqdn in the host "/etc/ovirt-hosted-engine/hosted-engine.conf" file. # cat /etc/ovirt-hosted-engine/hosted-engine.conf fqdn=<fqdn> <<======= here vm_disk_id=f27af8d0-b8b8-402b-9114-886bc9a98759 vm_disk_vol_id=3c25f27d-91bf-416d-bc31-a0f11dc245af vmid=88453282-193c-45d6-8944-ef8c8f8415b4 storage=<host_name>:/RHV4/HE_Data Steps to Reproduce: 1. Implement hosted einge setup 2. rename hostname of engine with ovirt-engine-rename tool. 3. Check cat /etc/ovirt-hosted-engine/hosted-engine.conf Actual results: The hostname in hosted engine host to monitor Hosted engine VM heath remains unchanged. Expected results: It should change. Additional info: Workaround is to manually update the file with correct hostname. 4. Why does the customer need this? (List the business requirements here) To enable HA for hosted engine VM for monitoring or service. 5. How would the customer like to achieve this? (List the functional requirements here) Change hostname in /etc/ovirt-hosted-engine/hosted-engine.conf file automatically after running ovirt-engine-rename or some other function. 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. Yes 7. Is there already an existing RFE upstream or in Red Hat Bugzilla? I filed bug but team asked me to report a feature request. So here it is. 8. Does the customer have any specific time-line dependencies and which release would they like to target (i.e. RHEL5, RHEL6)? No 9. Is the sales team involved in this request and do they have any additional input? No 10. List any affected packages or components. rhevm 11. Would the customer be able to assist in testing this functionality if implemented? Yes
The user should probably use 'hosted-engine --set-shared-config' with the right value for the initial answerfile but currently 'hosted-engine --set-shared-config' let the user just modify notifications related values.
Moving to 4.1.4 not being identified as a blocker for 4.1.3 and depending on bug #1457357 which hasn't been targeted yet.
Moving to verified forth to https://bugzilla.redhat.com/show_bug.cgi?id=1481123#c23
Shorted and safest version of a fixing workaround to be used on older 4.0 systems: dir=$(mktemp -d) && cd $dir IMAGEPATH=$(find /rhev/data-center/ -path "*/${sdUUID}/images/${conf_image_UUID}/${conf_volume_UUID}" -type f 2>>/dev/null) sudo -u vdsm dd if=$IMAGEPATH 2>/dev/null | tar -xvf - 2>>/dev/null # edit fhanswers.conf and fix OVEHOSTED_NETWORK/fqdn line # upload it back tar --blocking-factor=40 -cO * | sudo -u vdsm dd of=$IMAGEPATH
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:1471
BZ<2>Jira Resync