Problem:
Foreman supports the oVirt high availability option but it does not
set high availability on the VM created on the oVirt server. The
“High Availability” checkbox is set in the oVirt “Compute Profile” and
the “ha=1” value is passed to the hammer command shown below. After the VM has been created the “High Availability” checkbox is not enabled on the host in the Foreman UI. If the host is edited in the Foreman UI and the “High Availability” checkbox is enabled then Foreman does set high availability on the VM on the oVirt server. If the host is edited again in the Foreman UI the “High Availability” checkbox is not enabled. The Foreman UI did not retain the enabled “High Availability” value.
hammer host create --name “vmtest” --compute-attributes “ha=1, cores=1, socket=1, memory=4294967296, cluster=CLUSTER1, start=1” --hostgroup “HOSTGROUP1” --image “IMAGE1” --interface “compute_network=NETWORK1, managed=1, primary=1, provision=1, type=interface” --ip “xxx.xxx.xxx.xxx” --location “Default Location” --operatingsystem “CentOS_7_oVirt” --organization “Default Organization” --provision-method “image”
Foreman and Proxy versions:
Foreman 2.3.1
Distribution and version:
CentOS 7.8
Other relevant data:
oVirt 4.3.10