Provisioning units on vSphere triggers critical MAC address conflict alarm
Bug #1837346 reported by
Tim McNamara
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
As of Juju 2.6, we provision an instance by creating a VM, resizing its disk, then cloning it. That causes the original machine's MAC address to be copied. In practice this isn't an issue, because the temporary VM is deleted as soon as possible, but the vSphere operator still receives a "Critical" alarm.
| Changed in juju: | |
| milestone: | 2.7-beta1 → 2.7-rc1 |
| Changed in juju: | |
| assignee: | Tim McNamara (tim-clicks) → nobody |
| milestone: | 2.7-rc1 → none |
| importance: | High → Medium |
| tags: | added: usability |
Revision history for this message
| Christian Muirhead (2-xtian) wrote | #1 |
| Changed in juju: | |
| status: | Triaged → Fix Released |
| milestone: | none → 2.6.10 |
To post a comment you must log in.
I think this is resolved now - we don't assign network devices to templates, only at clone time, so there aren't two machines with the same mac.