Bug 2055901
| Summary: | when upgrading all hosts in cluster, pinned VMs are stopped, even when the check box for "Stop Pinned VMs" is cleared | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Daniel Whitley <dwhitley> |
| Component: | ovirt-ansible-collection | Assignee: | Martin Necas <mnecas> |
| Status: | CLOSED DUPLICATE | QA Contact: | Lucie Leistnerova <lleistne> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.4.9 | CC: | mavital, mnecas, mperina |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-03-01 16:06:45 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Infra | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
*** This bug has been marked as a duplicate of bug 2049286 *** I see that this was closed as a duplicate of 2049286, but I think they are different. For example, in 2049286 the check box for "Stop Pinned VMs" is not cleared, but in this BZ it is. Enabling/selecting "Stop Pinned VMs" versus disabling/deselecting "Stop Pinned VMs" seems like a different scenario to me. Please let me know if I'm mistaken or am just doing an inadequate job of describing the scenario. Thanks. The fix is the same as in BZ2049286, closing as duplicate *** This bug has been marked as a duplicate of bug 2049286 *** |
Description of problem: When Updating All Hosts in a Cluster in the RHV Adminstration Portal [1], the first option is to "Stop Pinned VMs." If you clear the associated check box, and manually stop pinned VMs on hosts selected to update, all pinned VMs are stopped. Version-Release number of selected component (if applicable): ovirt-engine-4.4.9.5-0.1.el8ev.noarch ovirt-ansible-collection-1.6.5-1.el8ev.noarch How reproducible: Every time. Steps to Reproduce: 1. Pin a VM on each of 3 hosts. 2. In the Administration Portal, click Compute → Clusters and select the cluster. 3. Click Upgrade. 4. Select TWO of the THREE hosts to update, then click Next. 5. Clear the check box for "Stop Pinned VMs." 6. (manually) Stop the pinned VMs on the TWO hosts selected to update. 7. Clear the check box for "Reboot After Upgrade" (potentially unrelated?) 8. Configure any other options and click Next. 9. Review the summary of the hosts and virtual machines that will be affected. 10. Click Upgrade. Actual results: The remaining, running pinned VM will be stopped, even on though the host was skipped and the check box for "Stop Pinned VMs" was cleared. Expected results: The remaining, running pinned VM would not be stopped. Additional info: This is an attempt to leave a pinned VM running during the Cluster Upgrade process. One of the pinned VMs is expected to always be running. References: [1] Updating All Hosts in a Cluster > https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html-single/upgrade_guide/index#Updating_all_hosts_in_a_cluster_minor_updates