Link layer device merge fails with "provider IDs not unique" on MAAS
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Joseph Phillips | ||
MAAS |
Expired
|
Undecided
|
Unassigned |
Bug Description
This error appeared while I was testing the following scenario:
Using the latest 2.9 edge snap for MAAS, I configured a KVM instance with two NICs and the created an OVS (2.9 MAAS feature) bridge using the 2nd NIC. The first NIC and the bridge were assigned to different spaces.
I added a machine to my juju cloud as follows
juju add-machine --constraints spaces=
For this scenario, I had to use the netplan from groovy to get the OVS bridge properly set up on the provisioned machine.
Once the machine comes up, the following error appears in the logs:
"juju.apiserver
I believe MAAS reports the same provider ID for the OVS bridge device and the eth device which is part of the bridge.
This might be potentially related to https:/
Changed in juju: | |
status: | New → Incomplete |
Changed in juju: | |
milestone: | 2.9-beta1 → 2.9-rc1 |
Changed in juju: | |
milestone: | 2.9-rc1 → none |
no longer affects: | juju/2.8 |
Changed in juju: | |
milestone: | none → 2.9.19 |
importance: | Undecided → High |
status: | Incomplete → In Progress |
Changed in juju: | |
milestone: | 2.9.19 → 2.9.20 |
Changed in juju: | |
milestone: | 2.9.20 → 2.9.21 |
Changed in juju: | |
milestone: | 2.9.21 → 2.9.22 |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
Added MAAS. Should we really be getting the same provider ID for the physical NIC and the bridge?