Bug 1561447 - VM with a lease manage to remove while the VM lease storage domain is not active
Summary: VM with a lease manage to remove while the VM lease storage domain is not active
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Storage
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.2.3
: ---
Assignee: Eyal Shenitzky
QA Contact: Evelina Shames
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-28 11:01 UTC by Eyal Shenitzky
Modified: 2018-05-10 06:34 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-05-10 06:34:09 UTC
oVirt Team: Storage
Embargoed:
rule-engine: ovirt-4.2+
ylavi: exception+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 89647 0 master MERGED core: verify lease storage domain is active before removing a VM 2018-04-03 12:49:10 UTC
oVirt gerrit 89758 0 ovirt-engine-4.2 POST core: verify lease storage domain is active before removing a VM 2018-04-03 12:58:44 UTC

Description Eyal Shenitzky 2018-03-28 11:01:09 UTC 
Description of problem:

When having a VM with a lease, the VM managed to remove from the data center even though the VM lease storage domain was on maintenance.

As similar to disks, when one of the storage domain that contains one of the VM disks is not active, the VM cannot be removed.

Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. Create a VM with a disk based on storage domain [A] and a lease based on storage domain [B]
2. Deactivate storage domain [B]
3. Remove the VM

Actual results:
The VM removed from the environment

Expected results:
The VM removal should be banned by an engine validation

Additional info:
Comment 1 Eyal Shenitzky 2018-03-28 11:01:52 UTC 
version - 4.3.0_master - from commit 431feb88ac66840b6ce62237f9219f4e89af1c4b
Comment 2 Sandro Bonazzola 2018-04-18 11:08:08 UTC 
All referenced patches are in merged state, should this move to modified?
Comment 3 Evelina Shames 2018-04-24 13:05:47 UTC 
Verified.
Engine: 4.2.3.2-0.1
Comment 4 Sandro Bonazzola 2018-05-10 06:34:09 UTC 
This bugzilla is included in oVirt 4.2.3 release, published on May 4th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.3 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.
Note You need to log in before you can comment on or make changes to this bug.