Bug 1336527
| Summary: | Cluster level can be changed while there are running VMs | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | emahoney | |
| Component: | ovirt-engine | Assignee: | Marek Libra <mlibra> | |
| Status: | CLOSED ERRATA | QA Contact: | Shira Maximov <mshira> | |
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | 3.6.5 | CC: | adevolder, agkesos, amarchuk, aperotti, bgraveno, emahoney, germano, gklein, gveitmic, inetkach, lsurette, mavital, mgoldboi, michal.skrivanek, mkalinin, pstehlik, rbalakri, Rhev-m-bugs, srevivo, tjelinek, ycui, ykaul | |
| Target Milestone: | ovirt-4.0.0-rc | Keywords: | Reopened, ZStream | |
| Target Release: | 4.0.0 | |||
| Hardware: | x86_64 | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: |
This update enforces that no virtual machines are running when changing the cluster compatibility level. This ensures that virtual machines do not cause non-deterministic issues while underlying devices/services have changed. All virtual machines in a cluster must be down before changing the cluster level.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1340345 1341023 (view as bug list) | Environment: | ||
| Last Closed: | 2016-08-23 20:39:34 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: | ||||
| Bug Depends On: | 1340345 | |||
| Bug Blocks: | 1341023 | |||
|
Description
emahoney
2016-05-16 17:54:35 UTC
Can you please provide more details for step 5? How exatly did tou do that, shutdown and edit VM and change its cluster? inter-cluster migration is not supported for anything else than 3.5 el6 to el7 migration. It's not supposed to change anything and once the VM is shut down it won't be able to start again on those host. You need to move the VM when it's shutdown to the new cluster, which will change configuration (network, machine type, etc) after further investigation we found out that editing cluster level is not blocked when VMs are running. Several things are checked by bug 1298487 but this basic case is not applied. We need to check any non-Down state and block on it (In reply to Michal Skrivanek from comment #4) > after further investigation we found out that editing cluster level is not > blocked when VMs are running. Several things are checked by bug 1298487 but > this basic case is not applied. We need to check any non-Down state and > block on it AFAIR, we REALLY do not want to enforce all VMs to be down when changing cluster level - was that ever a requirement? Verified on: oVirt Engine Version: 4.1.0-0.0.master.20160605051229.gitb398fa2.el7.centos Verification steps: 1. Create a DC with 3.6 compatibility version 2. Add a host with 3.6 compatibility version 3. Create and run vm 4. Try to edit the 3.6 compatibility version in cluster from 3.6 to 4.0 Result : 'shut down all vm before changing the cluster level' Removing the doc text since this feature is changed by #1356027 and especially gerrit 61079 . Recent behavior: Cluster version change is allowed in Cluster Edit dialog even if there are running/suspended VMs. These not-down VMs are marked by NextRun configuration icon. VM Custom compatibility level is set to original cluster version until shut down+restart. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2016-1743.html |