Bug 1847513
| Summary: | [UPGRADE] failed to change the cluster compatibility version from 4.3 > 4.4 while VMs running on the cluster. | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Kobi Hakimi <khakimi> |
| Component: | BLL.Virt | Assignee: | Liran Rotenberg <lrotenbe> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Nikolai Sednev <nsednev> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.4.1.2 | CC: | aoconnor, bugs, lrotenbe, michal.skrivanek, nsednev, pmatyas, rdlugyhe, rhodain |
| Target Milestone: | ovirt-4.4.1 | Keywords: | AutomationBlocker, Triaged |
| Target Release: | 4.4.1.5 | Flags: | pm-rhel:
ovirt-4.4+
aoconnor: blocker+ |
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ovirt-engine-4.4.1.5 | Doc Type: | Bug Fix |
| Doc Text: |
When you change the cluster compatibility version, it can also update the compatibility version of the virtual machines. If the update fails, it rolls back the changes. Previously, chipsets and emulated machines were not part of the cluster update. The current release fixes this issue. Now, you can also update chipsets and emulator machines when you update the cluster compatibility version.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-07-08 08:26:53 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
Kobi Hakimi
2020-06-16 14:21:08 UTC
logs? Works for me on latest Software Version:4.4.1.7-0.3.el8ev. ovirt-hosted-engine-ha-2.4.4-1.el8ev.noarch ovirt-hosted-engine-setup-2.4.5-1.el8ev.noarch Linux 4.18.0-193.12.1.el8_2.x86_64 #1 SMP Thu Jul 2 15:48:14 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Red Hat Enterprise Linux release 8.2 (Ootpa) Reported issue no longer exists. This bugzilla is included in oVirt 4.4.1 release, published on July 8th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.1 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. *** Bug 1856791 has been marked as a duplicate of this bug. *** |