maas aborted transaction trying to update link layer device
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Joseph Phillips |
Bug Description
In a model we were seeing two link layer devices with the same provider id (the example we were seeing was a nic and a bridge on that nic). In that situation, when we try to call Machine.
Reading SetLinkLayerDevices it's doing some uniqueness checking against the provider ids already in the db, but it doesn't look like it's checking whether the provider IDs on the link layer devices passed in are unique. We need to decide how to handle that case.
This was on MAAS 1.9, not sure whether it's specific to 1.9 or not.
Changed in juju: | |
assignee: | nobody → Joseph Phillips (manadart) |
status: | New → Triaged |
importance: | Undecided → Critical |
milestone: | none → 2.5-rc1 |
Changed in juju: | |
importance: | Critical → High |
Changed in juju: | |
milestone: | 2.5-rc1 → 2.5.1 |
Changed in juju: | |
milestone: | 2.5.1 → 2.5.2 |
Changed in juju: | |
assignee: | Joseph Phillips (manadart) → nobody |
Changed in juju: | |
milestone: | 2.5.2 → 2.5.3 |
Changed in juju: | |
milestone: | 2.5.3 → 2.5.4 |
Changed in juju: | |
milestone: | 2.5.4 → 2.5.5 |
Changed in juju: | |
milestone: | 2.5.6 → 2.5.8 |
Changed in juju: | |
milestone: | 2.5.8 → 2.5.9 |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
Is there any more detail we can get around steps to reproduce?
Series in use, what NICs are on the host?