Bug 905743 - guest MAC address conflicts encountered when guest recipe finishes before host recipe
Summary: guest MAC address conflicts encountered when guest recipe finishes before hos...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: scheduler
Version: 0.10
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: HOTFIX
Assignee: Dan Callaghan
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-30 04:35 UTC by Dan Callaghan
Modified: 2018-02-06 00:41 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 903893
Environment:
Last Closed: 2013-01-31 05:42:13 UTC
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.