Description of problem: When setting up HE env, there is no option to select cluster CPU type and it is selected according to the first host. This can lead to unusable environments. If I add the best host first I will never be able to add older hosts as the CPU type cannot be changed (lowered) as HE VM is always up. Version-Release number of selected component (if applicable): ovirt-hosted-engine-setup-2.4.4-1.el8ev.noarch How reproducible: always Steps to Reproduce: 1. set up HE 2. 3. Actual results: cluster CPU type is selected according to the first host Expected results: there needs to be an option to select cluster CPU type Additional info: not sure what was selected before (maybe lowest?)
That”s the same behavior as within regular webadmin
No it's not, within regular webadmin you can change the cluster cpu level before adding hosts and pick the lowest one necessary. Also please specify priority, severity is for QE. This is blocking issue for our environments as we can't use virtual hosts when we start with adding regular ones.
This though probably need an question in HE-setup as well
Petr, feel free to post a patch for that, I don't see a reason why it couldn't be added as another low level setting variable in ovirt-ansible-hosted-engine-setup.
I've memories of this question being there in the past. Need to check why it got removed or not exposed.
Also we need to check if we can change this setting after HE is deployed. If this can be done in a second step we can just close this bug.
still not really within out capacity. See comment #4, it's either going to happen by contribution in foreseeable future or it will get closed for no activity
the fix was released on 4th May (https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/releases/tag/1.1.3).
Fix was done only for running the playbook directly. As there is no question in HE setup then this will need further patches and IMO this is not enough to verify this bug now, as it was reported mainly for the manual setup.
Not blocking 4.4.1 on this bug and 4.4.2 has been already planned, moving to 4.4.3 for zstream consideration.
Unfortunately, I don't see inside engine-setup code
Is this already fixed in 4.4.2?
It is fixed in 4.4.2 only when running the playbook directly (see comment 11). In the last ovirt-hosted-engine-setup build (2.4.6), there is an option to pass ansible vars (fixed in bug 1849517) when running 'hosted-engine --deploy'.
So using ansible extra vars works without a problem, however the setting of cluster CPU doesn't work as it still is an edit and not set during setup. # hosted-engine --deploy --ansible-extra-vars=he_cluster_cpu_type='Intel Nehalem Family' # I have host that has Westmere cluster CPU to recognize if there was some change however this only results in: [ INFO ] TASK [ovirt.hosted_engine_setup : Ensure that the target cluster is present in the target datacenter] [ ERROR ] ovirtsdk4.Error: Fault reason is "Operation Failed". Fault detail is "[Cannot change Cluster CPU type unless all Hosts attached to this Cluster are in Maintenance.]". HTTP response code is 409. [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Fault reason is \"Operation Failed\". Fault detail is \"[Cannot change Cluster CPU type unless all Hosts attached to this Cluster are in Maintenance.]\". HTTP response code is 409."}
too late for 4.4.2
Not cirtical, moved out to 4.4.4.
This works when using @varfile with a full path. #hosted-engine --deploy --ansible-extra-vars=@/root/a.json
Verified with ovirt-ansible-collection-1.2.2-1.el8ev.noarch [root@host ~]# cat deploy.json { "he_cluster_cpu_type": "Intel Nehalem Family" } [root@host ~]# hosted-engine --deploy --ansible-extra-vars=@/root/deploy.json Results in Default cluster having Nehalem instead of max level possible which is Westmere. [root@host ~]# lscpu Model name: Westmere E56xx/L56xx/X56xx (Nehalem-C)