Description of problem: I have 3.5 SHE EL6 host with engine 3.6.8 and I tried to deploy an EL7 3.5 host as another SHE host (into Default cluster which is in InClusterUpgrade scheduling policy). I do this is a step before migration whole 3.5 SHE env to 3.6. In the end of hosted-engine --deploy there are errors even the whole process seems to finish OK - at least I see the host up in engine and visible in hosted-engine --vm-status. ~~~ 2016-08-05 20:11:20 INFO otopi.plugins.ovirt_hosted_engine_setup.engine.add_host add_host._wait_host_ready:200 The VDSM Host is now operational 2016-08-05 20:11:20 DEBUG otopi.plugins.ovirt_hosted_engine_setup.engine.add_host add_host._closeup:691 Setting CPU for the cluster 2016-08-05 20:11:21 DEBUG otopi.plugins.ovirt_hosted_engine_setup.engine.add_host add_host._closeup:697 {'name': None, 'level': None, 'cpu_tune': None, 'architecture': 'X86_64', 'mode': None, 'cores': None, 'spee d': None, 'id': 'Intel Westmere Family', 'topology': None} 2016-08-05 20:11:21 DEBUG otopi.plugins.ovirt_hosted_engine_setup.engine.add_host add_host._closeup:708 Cannot set CPU level of cluster Default Traceback (most recent call last): File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/ovirt-hosted-engine-setup/engine/add_host.py", line 702, in _closeup cluster.update() File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/brokers.py", line 358, in update headers={"Correlation-Id":correlation_id} File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py", line 78, in update return self.request('PUT', url, body, headers) File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py", line 118, in request persistent_auth=self._persistent_auth) File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py", line 146, in __doRequest persistent_auth=persistent_auth File "/usr/lib/python2.7/site-packages/ovirtsdk/web/connection.py", line 134, in doRequest raise RequestError, response RequestError: status: 400 reason: Bad Request detail: inclusterupgrade is not a member of SchedulingPolicyType. Possible values for SchedulingPolicyType are: evenly_distributed, power_saving, none, vm_evenly_distributed 2016-08-05 20:11:21 ERROR otopi.plugins.ovirt_hosted_engine_setup.engine.add_host add_host._closeup:716 Cannot automatically set CPU level of cluster Default: inclusterupgrade is not a member of SchedulingPolicyType. Possible values for SchedulingPolicyType are: evenly_distributed, power_saving, none, vm_evenly_distributed ~~~ Version-Release number of selected component (if applicable): ovirt-hosted-engine-setup-1.2.6.1-1.el7ev.noarch How reproducible: right now Steps to Reproduce: 1. SHE env - 3.5 EL6 host, engine 3.6 with InClusterUpgrade sched. policy 2. have EL7 host with 3.5 rpms (cannot go directly to 3.6 rpms) 3. hosted-engine --deploy Actual results: some strange error about policy and scheduling policy Expected results: either error should make the process fail or just warning of be silent Additional info: imo all checks should be done in advance before doing any practical activity ;)
As mentioned in the other bz, the clean upgrade path is: 3.5/el6 -> 3.5/el7 -> 3.6/el7...
I don't understand how I could have all SHE hosts in 3.5 with EL7 if I have started with 3.5 EL6. If I have 2 SHE hosts with 3.5 EL6, I would need to remove one, reinstall it to 3.5 EL7, add it back to SHE "cluster" so the HE VM could be migrated from 3.5 EL6 to this new 3.5 EL7. This is a necessary precondition to "migrate" (ie. remove, reinstall to EL7, add back to SHE "cluster") existing 3.5 EL6 host to 3.5 EL7. I could not have the HE VM running on nowhere, if I have existing 3.5 EL6 SHE setup, this is where I must start from.
If you turn off the VM it will start on the next available HE node. In your case it's the latest 3.5/le7 which is what you want.