Bug 1142935
| Summary: | Assigned to running VMs CPU profile may be deleted and then being wiped out from all running VMs. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Nikolai Sednev <nsednev> | ||||
| Component: | General | Assignee: | Roman Mohr <roman> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Nikolai Sednev <nsednev> | ||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | --- | CC: | amarchuk, bugs, dfediuck, gklein, lpeer, mavital, mgoldboi, rbalakri, rgolan, Rhev-m-bugs, rmohr, roman, sherold, yeylon, ykaul | ||||
| Target Milestone: | ovirt-3.6.3 | Keywords: | Triaged | ||||
| Target Release: | 3.6.3 | Flags: | rule-engine:
ovirt-3.6.z+
mgoldboi: blocker+ rule-engine: planning_ack+ rgolan: devel_ack+ mavital: testing_ack+ |
||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | sla | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: |
Cause:
CPU and Disk profiles could be deleted although they were still in use by VMs or disks.
Consequence:
The profiles were removed from VMs and disks without any notice.
Fix:
Check if profiles are still in use.
Result:
User will be informed which VMs and disks are still using a profile. Only when it is unused the deletion will succeed.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-02-18 11:16:47 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | SLA | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
Removing a profile is not a problem. The running VM can either keep the limitation or become unlimited. this is an automated message. oVirt 3.6.0 RC3 has been released and GA is targeted to next week, Nov 4th 2015. Please review this bug and if not a blocker, please postpone to a later release. All bugs not postponed on GA release will be automatically re-targeted to - 3.6.1 if severity >= high - 4.0 if severity < high Should this be modified? Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release. This bug is not marked for z-stream, yet the milestone is for a z-stream version, therefore the milestone has been reset. Please set the correct milestone or add the z-stream flag. Bug tickets that are moved to testing must have target release set to make sure tester knows what to test. Please set the correct target release before moving to ON_QA. Bug tickets that are moved to testing must have target release set to make sure tester knows what to test. Please set the correct target release before moving to ON_QA. Followed the reproduction steps and after I tried to remove the CPU profile named Test, received this message: Error while executing action: Cannot remove CPU Profile. Several virtual machines (1) are using this Profile: RHEL7_2_VM1 - Please remove it from all virtual machines that are using it and try again. Works for me on these components: Host: libvirt-client-1.2.17-13.el7_2.3.x86_64 qemu-kvm-rhev-2.3.0-31.el7_2.7.x86_64 ovirt-vmconsole-1.0.0-1.el7ev.noarch ovirt-vmconsole-host-1.0.0-1.el7ev.noarch sanlock-3.2.4-2.el7_2.x86_64 mom-0.5.2-1.el7ev.noarch vdsm-4.17.19-0.el7ev.noarch Linux version 3.10.0-327.10.1.el7.x86_64 (mockbuild.eng.bos.redhat.com) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-4) (GCC) ) #1 SMP Sat Jan 23 04:54:55 EST 2016 Engine: ovirt-host-deploy-java-1.4.1-1.el6ev.noarch ovirt-setup-lib-1.0.1-1.el6ev.noarch rhevm-3.6.3-0.1.el6.noarch ovirt-vmconsole-proxy-1.0.0-1.el6ev.noarch ovirt-engine-extension-aaa-jdbc-1.0.5-1.el6ev.noarch ovirt-vmconsole-1.0.0-1.el6ev.noarch ovirt-host-deploy-1.4.1-1.el6ev.noarch Linux version 2.6.32-573.12.1.el6.x86_64 (mockbuild.eng.bos.redhat.com) (gcc version 4.4.7 20120313 (Red Hat 4.4.7-16) (GCC) ) #1 SMP Mon Nov 23 12:55:32 EST 2015 |
Created attachment 938526 [details] logs Description of problem: Assigned to running VMs CPU profile may be deleted and then being wiped out from all running VMs. Version-Release number of selected component (if applicable): dhcp163-77.scl.lab.tlv.redhat.com sanlock-3.1.0-2.el7.x86_64 qemu-kvm-rhev-1.5.3-60.el7_0.2.x86_64 vdsm-4.16.4-0.el7.x86_64 libvirt-daemon-1.1.1-29.el7_0.1.x86_64 libvirt-daemon-driver-secret-1.1.1-29.el7_0.1.x86_64 libvirt-daemon-driver-storage-1.1.1-29.el7_0.1.x86_64 libvirt-daemon-driver-qemu-1.1.1-29.el7_0.1.x86_64 libvirt-python-1.1.1-29.el7_0.1.x86_64 libvirt-lock-sanlock-1.1.1-29.el7_0.1.x86_64 libvirt-daemon-kvm-1.1.1-29.el7_0.1.x86_64 libvirt-client-1.1.1-29.el7_0.1.x86_64 libvirt-daemon-driver-interface-1.1.1-29.el7_0.1.x86_64 libvirt-daemon-driver-nodedev-1.1.1-29.el7_0.1.x86_64 libvirt-daemon-config-nwfilter-1.1.1-29.el7_0.1.x86_64 libvirt-daemon-driver-network-1.1.1-29.el7_0.1.x86_64 libvirt-daemon-driver-nwfilter-1.1.1-29.el7_0.1.x86_64 How reproducible: 100% Steps to Reproduce: 1.Create number of VMs and CPU profile. 2.Assign to all VMs created CPU profile and run them all. 3.Check that all VMs are running with assigned to them CPU profile. 4.Delete CPU profile. Actual results: Cpu profile deleted, while being used on running VMs. Expected results: CPU profile should not be deleted, while being assigned to any running/not running VM. Additional info: logs