Back to bug 1317447

Who When What Removed Added
Yaniv Lavi 2016-03-14 10:17:24 UTC Assignee sherold danken
Dan Kenigsberg 2016-03-31 12:55:37 UTC Target Milestone ovirt-4.0.0 ovirt-4.1.0
Flags ovirt-4.0.0? ovirt-4.1.0?
John Skeoch 2016-04-18 07:33:10 UTC CC yeylon srevivo
Yaniv Lavi 2016-07-20 09:40:29 UTC Priority medium high
Dan Kenigsberg 2016-07-27 08:49:17 UTC Assignee danken yzaspits
Michael Burman 2016-08-25 07:59:08 UTC CC mburman
Docs Contact mburman
Michael Burman 2016-09-01 12:52:17 UTC Docs Contact mburman
Gil Klein 2016-11-01 11:46:26 UTC QA Contact gklein myakove
Michael Burman 2016-11-15 06:04:08 UTC Flags testing_plan_complete+
Meni Yakove 2016-11-15 11:23:24 UTC Flags testing_ack? testing_ack+
Red Hat Bugzilla Rules Engine 2016-11-15 12:19:51 UTC Flags ovirt-4.1? ovirt-4.1+
Yaniv Lavi 2016-11-30 09:18:30 UTC CC lzitnits
Yaniv Lavi 2016-11-30 09:46:19 UTC Status NEW POST
Yaniv Lavi 2016-12-08 14:38:18 UTC Link ID oVirt gerrit 67593
Target Milestone ovirt-4.1.0-alpha ovirt-4.1.0-beta
Yaniv Kaul 2016-12-22 13:44:54 UTC Link ID oVirt gerrit 68557
Link ID oVirt gerrit 68558
Link ID oVirt gerrit 68034
Target Milestone ovirt-4.1.0-beta ovirt-4.2.0
Flags needinfo?(ydary)
Red Hat Bugzilla Rules Engine 2016-12-22 13:45:03 UTC Flags ovirt-4.1+ ovirt-4.2? ovirt-4.2? ovirt-4.2+
Yaniv Lavi 2016-12-22 13:53:22 UTC Target Milestone ovirt-4.2.0 ovirt-4.1.0-beta
Flags needinfo?(ydary) ovirt-4.2+ ovirt-4.1+
Dan Kenigsberg 2017-01-08 13:30:04 UTC Link ID oVirt gerrit 69302
Link ID oVirt gerrit 69303
Link ID oVirt gerrit 69304
Link ID oVirt gerrit 69305
Status POST MODIFIED
Status MODIFIED ON_QA
Michael Burman 2017-01-08 13:46:27 UTC Status ON_QA VERIFIED
Sandro Bonazzola 2017-01-23 10:03:28 UTC Target Release --- 4.1.0.2
Yevgeny Zaspitsky 2017-01-25 13:58:35 UTC Doc Text Feature:
The feature allows a user to request oVirt to assign a new MAC address in the flow of importing a VM from a data storage domain (Disaster recovery) and the current MAC address is bad.

Reason:
Importing a VM with a bad MAC address might cause MAC collision in the target LAN.
A MAC address would be considered as "bad" when it is in use already in the target oVirt cluster or it is out of the range of the mac pool of the target cluster.

Result:
A user is able to request oVirt to assign a new MAC address in the flow of importing a VM from a data storage domain.
Sandro Bonazzola 2017-02-01 14:52:26 UTC Status VERIFIED CLOSED
Resolution --- CURRENTRELEASE
Last Closed 2017-02-01 09:52:26 UTC
Tahlia Richardson 2017-02-10 02:02:50 UTC CC trichard
Doc Text Feature:
The feature allows a user to request oVirt to assign a new MAC address in the flow of importing a VM from a data storage domain (Disaster recovery) and the current MAC address is bad.

Reason:
Importing a VM with a bad MAC address might cause MAC collision in the target LAN.
A MAC address would be considered as "bad" when it is in use already in the target oVirt cluster or it is out of the range of the mac pool of the target cluster.

Result:
A user is able to request oVirt to assign a new MAC address in the flow of importing a VM from a data storage domain.
This feature allows you to request a new MAC address when importing a virtual machine from a data storage domain. This allows you to avoid importing a virtual machine with a bad MAC address, which might cause MAC collision in the target LAN. A MAC address would be considered "bad" when it is in use already in the target cluster, or it is out of the range of the MAC pool of the target cluster.
Tahlia Richardson 2017-02-10 05:57:20 UTC Blocks 1421009
Lucy Bopf 2017-03-01 04:21:58 UTC Blocks 1421425

Back to bug 1317447