Bug 1482569 - Force remove of a storage domain should release MAC addresses only for VMs which are removed from the setup
Summary: Force remove of a storage domain should release MAC addresses only for VMs wh...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Backend.Core
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ovirt-4.1.6
: 4.1.6
Assignee: Maor
QA Contact: Elad
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-17 15:18 UTC by Maor
Modified: 2017-09-19 10:02 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-09-19 10:02:51 UTC
oVirt Team: Storage
Embargoed:
rule-engine: ovirt-4.1+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 80752 0 master MERGED core: Release mac pools only VMs with disks on removed SD. 2017-08-20 12:42:11 UTC
oVirt gerrit 80822 0 ovirt-engine-4.1 MERGED core: Release mac pools only VMs with disks on removed SD. 2017-08-21 12:38:17 UTC

Description Maor 2017-08-17 15:18:37 UTC 
Description of problem:
As part of the fix for BZ1475272, force remove of a storage domain will free all MAC addresses which are related to a storage pool.
The engine should only free mac addresses of VMs which have disks on this storage domain and will be removed once this storage domain will be removed.

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


How reproducible:


Steps to Reproduce:
1. Add 3 storage domain
2. Add VM1 with disk on storage domain 1 use mac pool address for this VM
3. Add VM2 with disk on storage domain 2 and use another mac pool address for this VM
4. Force remove storage domain1

Actual results:
the mac address of VM1 and VM2 will be released

Expected results:
the mac address of VM1 should be released, VM2 should stay the same.

Additional info:
Comment 1 Elad 2017-08-30 10:24:37 UTC 
Tested the scenario from the description.

After force remove of domain1, the MAC of VM1 is released and can be used for new vNIC creation and the MAC for VM2 is not released and cannot be allocated for another vNIC.

Tested using:
rhevm-4.1.6-0.1.el7.noarch
Note You need to log in before you can comment on or make changes to this bug.