Description of problem: When creating a pool there is no High Available tab. But then in the created VM it is existent and available for configuration ( 'Resume behavior' is disabled). Such VM configured as HA brings a validation error on start "Cannot run VM. Highly Available Virtual servers can not be run as stateless". As we are not expecting from stateless VMs to be HA, this configuration must be disabled for them Version-Release number of selected component (if applicable): http://bob-dr.lab.eng.brq.redhat.com/builds/4.4/rhv-4.4.0-18 How reproducible:100% Steps to Reproduce: 1.Create new pool 2.Edit the created VM , check 'Highly Available' 3.Start the VM. Actual results:2020-02-09 18:22:01,141+02 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-60) [83cd6a22-19f7-4325-8836-b30198eeb6a2] EVENT_ID: USER_FAILED_RUN_VM(54), Failed to run VM pool-1 due to a failed validation: [Cannot run VM. Highly Available Virtual servers can not be run as stateless.] Expected results: As we are not expecting from stateless VMs to be HA , this configuration must be disabled for them Additional info:
I reviewed this issue. The error message is named EngineMessage.VM_CANNOT_RUN_STATELESS_HA, so the error states that stateless VMs do not run as stateless: Highly Available Virtual servers can not be run as stateless. The definition of a VM in a VM pool is as follows: Virtual machines in a virtual machine pool are stateless, meaning that data is not persistent across reboots. However, if a user configures console options for a virtual machine taken from a virtual machine pool, those options will be set as the default for that user for that virtual machine pool. [1] [1] https://www.ovirt.org/documentation/admin-guide/chap-Pools.html Please clarify what needs to be changed and why.
This was already clarified. When a pool VM is spawned, it can be edited outside of the pool during its lifecycle. We should not allow VMs whose origin is a pool to select HA options
Ryan, Polina, there are more fields that are not disabled for VMs in pool - could you check if that is correct? Initial run - Use Cloud-Init/Sysprep - VM Hostname - Configure Time Zone - Authentication - all fields - Networks - all fields except In-guest Network Interface Name - Custom script High Availability - Target Storage Domain for VM Lease - Priority - Watchdog Model (note that Watchdog Action is disabled) Resource allocation - CPU Shares - Memory Balloon Device - Multi Queues enabled - VirtIO-SCSI Enabled Boot options: - Enable menu to select boot device Foreman / Satelite - Provider
The rest of these should be ok, since they're editable properties which don't affect VM invocation (and the HA options listed should be disabled now)
change SLA team to virt, we're not tracking SLA separately anymore
verified on http://bob-dr.lab.eng.brq.redhat.com/builds/4.4/rhv-4.4.0-23
This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.0 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.