maas aborted transaction trying to update link layer device

Bug #1805966 reported by Christian Muirhead on 2018-11-30
This bug affects 1 person
Affects Status Importance Assigned to Milestone

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.SetLinkLayerDevices Machine.updateLinkLayerDeviceOps produces a transaction with an assertion that the providerIDs record doesn't exist - this fails because it's already associated with the other device.

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
Joseph Phillips (manadart) wrote :

Is there any more detail we can get around steps to reproduce?

Series in use, what NICs are on the host?

Changed in juju:
importance: Critical → High
Christian Muirhead (2-xtian) wrote :

Sorry, here's some more info from Xav Paice - this is from a client site, so I'll leave it on rather than copying it in here.

The transaction that was failing:

Network info for the machine:

MAAS info:

Changed in juju:
milestone: 2.5-rc1 → 2.5.1
Ian Booth (wallyworld) on 2019-01-28
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
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers