Bug 1801205
Summary: | HA configuration for VMs in a pool must be disabled - causes confusing behavior | ||
---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | Polina <pagranat> |
Component: | BLL.Virt | Assignee: | Steven Rosenberg <srosenbe> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | meital avital <mavital> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.4.0 | CC: | bugs, ljelinko, mtessun, rbarry, rdlugyhe, srosenbe |
Target Milestone: | ovirt-4.4.0 | Flags: | pm-rhel:
ovirt-4.4+
|
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | ovirt-engine-4.4.0 gitb5b5c99ca2f | Doc Type: | Bug Fix |
Doc Text: |
Previously, VM Pools set to HA could no be run. VM Pools are stateless. Nonetheless, a user could set a VM in a Pool as supporting HA, but then the VM could not be launched. The current release fixes this issue: It disables the HA checkbox so that the user can no longer set VM Pools to support HA. As a result, the user can no longer set a VM Pool to support HA.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2020-05-20 20:00:23 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Polina
2020-02-10 12:09:15 UTC
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 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. |