Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 873338 - MAC address shouldn't be freed when performing snapshot preview
MAC address shouldn't be freed when performing snapshot preview
Status: CLOSED CURRENTRELEASE
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine (Show other bugs)
3.1.0
x86_64 Linux
medium Severity high
: ---
: 3.2.0
Assigned To: Moti Asayag
GenadiC
network
:
: 873237 (view as bug list)
Depends On:
Blocks: 948448
  Show dependency treegraph
 
Reported: 2012-11-05 10:25 EST by GenadiC
Modified: 2016-02-10 14:54 EST (History)
11 users (show)

See Also:
Fixed In Version: sf13.1
Doc Type: Release Note
Doc Text:
If a virtual machine had a different number of network interfaces in normal mode and in snapshot preview mode, unused MAC addresses in either mode would be released to the pool. This meant that the same MAC address could potentially be assigned to network interfaces belonging to different virtual machines. With this update, a check is performed when a network interface is being plugged to ensure that it is not assigned an already used MAC address.
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Network
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 12241 None None None Never

  None (edit)
Description GenadiC 2012-11-05 10:25:28 EST
Description of problem:

Suppose you have VM with 2 MAC addresses on its 2 NICs (MAC_A and MAC_B) and its Snapshot have only one MAC on its NIC (MAC_A), then performing preview from snapshot will release MAC_B to the pool, so you can assign it to other NICs on other VMs.
As a result you can get a situation where you have 2 VMs with the same MAC address assigned to its NICs


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


How reproducible:
Always

Steps to Reproduce:
1. Create VM_1 with MAC_A on nic1
2. Create snapshot from VM_1
3. Add to VM_1 MAC_B on nic2
4. Preview VM1 from the snapshot
5. Add MAC_B on one of the NICs of another VM
6. Perform undo for the snapshot of VM_1 from preview mode
  
Actual results:
VM_1 and VM_2 will have MAC_B on its NICs

Expected results:
You are not supposed to have 2 VMs with the same MAC

Additional info:
Comment 2 Moti Asayag 2013-04-04 05:59:22 EDT
*** Bug 873237 has been marked as a duplicate of this bug. ***
Comment 3 Dan Kenigsberg 2013-04-04 06:33:09 EDT
If someone plays with teh global allow/disallow flag, and two VMs with duplicate mac addresses exist, we shuld add a similar can-do-action to ensure that only one of these machines is currently running.
Comment 4 GenadiC 2013-04-15 02:23:02 EDT
Verified on rhevm-3.2.0-10.19.beta2.el6ev.noarch
Comment 5 Itamar Heim 2013-06-11 04:40:56 EDT
3.2 has been released
Comment 6 Itamar Heim 2013-06-11 04:41:03 EDT
3.2 has been released
Comment 7 Itamar Heim 2013-06-11 04:41:05 EDT
3.2 has been released
Comment 8 Itamar Heim 2013-06-11 04:48:28 EDT
3.2 has been released

Note You need to log in before you can comment on or make changes to this bug.