Red Hat Bugzilla – Bug 1279548
[upgrade] broker.conf got overwritten with initial defaults during 3.5 -> 3.6 upgrade
Last modified: 2017-01-23 21:35:03 EST
Description of problem:
in 3.6 broker.conf got moved to the shared storage and periodically copied to /var/lib/ovirt-hosted-engine-ha/broker.conf for caching purposes and to be able to send notification also when the shared storage goes down; during a 3.5 -> 3.6 upgrade, broker.conf got overwritten with initial defaults
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. upgrade form 3.5 to 3.6
2. check /var/lib/ovirt-hosted-engine-ha/broker.conf
broker.conf on the shared storage got written with the initial defaults
broker.conf on the shared storage got written with the values it had just before the upgrade.
Ho to fix the copy on the shared storage if it's already happened:
dir=`mktemp -d` && cd $dir
systemctl stop ovirt-ha-broker
sdUUID_line=$(grep sdUUID /etc/ovirt-hosted-engine/hosted-engine.conf)
conf_volume_UUID_line=$(grep conf_volume_UUID /etc/ovirt-hosted-engine/hosted-engine.conf)
conf_image_UUID_line=$(grep conf_image_UUID /etc/ovirt-hosted-engine/hosted-engine.conf)
dd if=/rhev/data-center/mnt/192.168.1.115:_Virtual_ext35u36/$sdUUID/images/$conf_image_UUID/$conf_volume_UUID 2>/dev/null| tar -xvf -
cp /etc/ovirt-hosted-engine-ha/broker.conf.rpmsave broker.conf # or edit broker.conf as you need
tar -cO * | dd of=/rhev/data-center/mnt/192.168.1.115:_Virtual_ext35u36/$sdUUID/images/$conf_image_UUID/$conf_volume_UUID
systemctl start ovirt-ha-broker
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.
This bug is not marked for z-stream, yet the milestone is for a z-stream version, therefore the milestone has been reset.
Please set the correct milestone or add the z-stream flag.
Verified on ovirt-hosted-engine-ha-188.8.131.52-1.el7ev.noarch
After upgrade of packages and restart /var/lib/ovirt-hosted-engine-ha/broker.conf content equal to /etc/ovirt-hosted-engine-ha/broker.conf in 3.5
According to verification status and target milestone this issue should be fixed in oVirt 3.6.1. Closing current release.