Bug 905743

Summary:	guest MAC address conflicts encountered when guest recipe finishes before host recipe
Product:	[Retired] Beaker	Reporter:	Dan Callaghan <dcallagh>
Component:	scheduler	Assignee:	Dan Callaghan <dcallagh>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	0.10	CC:	asaha, dcallagh, jburke, jstancek, ltoscano, mishin, qwan, rglasz, rmancy, trusnak
Target Milestone:	HOTFIX
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	903893	Environment:
Last Closed:	2013-01-31 05:42:13 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Dan Callaghan 2013-01-30 04:35:15 UTC

+++ This bug was initially created as a clone of Bug #903893 +++

--- Additional comment from Dan Callaghan on 2013-01-30 12:37:33 EST ---

So I finally figured out that the actual most common cause of these duplicate MAC addresses is a simpler (and way nastier) bug than described in comment #0 (powering on machines after Beaker has returned them).

Namely, we are re-using MAC addresses as soon as the recipe has finished -- but if the *recipe set* is still running (for example, because the host recipe has /distribution/reservesys) then the guest could still very well be running with the same MAC address.

At the very least, we need to only re-use the MAC address once the entire recipe set has finished. We should still also consider some of the ideas above, for mitigating the problem described in comment #0.

Comment 1 Dan Callaghan 2013-01-30 04:43:40 UTC

On Gerrit: http://gerrit.beaker-project.org/1674

Comment 2 Dan Callaghan 2013-01-31 05:42:13 UTC

Beaker 0.11.2 hot fix has been released.