Link layer device merge fails with "provider IDs not unique" on MAAS

Bug #1898195 reported by Achilleas Anagnostopoulos
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Undecided
Unassigned
juju
Undecided
Joseph Phillips
2.8
High
Joseph Phillips

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=space1,space2 --series=groovy

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.instancepoller link layer device merge attempt for machine 4 failed due to error: provider IDs not unique: 10; waiting until next instance-poller run to retry"

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://bugs.launchpad.net/bugs/1805966

Revision history for this message
Joseph Phillips (manadart) wrote :

Added MAAS. Should we really be getting the same provider ID for the physical NIC and the bridge?

Revision history for this message
Adam Collard (adam-collard) wrote :

Can you share info of what Juju is trying to do around the 'link layer device merge attempt'?

Also please share interface info from the MAAS API a la:

$ maas $PROFILE interfaces read $SYSTEM_ID

Revision history for this message
Achilleas Anagnostopoulos (achilleasa) wrote :

I just recreated my deployment and didn't hit the merge error this time. I will try a few more times and provide additional information from both the juju-db and MAAS if I manage to reproduce again.

Revision history for this message
Björn Tillenius (bjornt) wrote :

Indeed, API output would be good. Also, how does Juju calculate/get the provider id? MAAS has no concept of a provider ID, so I'm not sure what you're talking about exactly.

Changed in maas:
status: New → Incomplete
Revision history for this message
John A Meinel (jameinel) wrote : Re: [Bug 1898195] Re: Link layer device merge fails with "provider IDs not unique" on MAAS

gomaasapi has
Machine with method InterfaceSet() []Interface

That Interface object has:
type Interface interface {
ID() int
Name() string
// The parents of an interface are the names of interfaces that must exist
// for this interface to exist. For example a parent of "eth0.100" would be
// "eth0". Parents may be empty.
Parents() []string

The Interface.ID() is what we are calling provider id internally.
(eg, the ID returned by the provider for the interface is the ProviderID of
that interface)

On Tue, Oct 6, 2020 at 3:11 AM Björn Tillenius <email address hidden>
wrote:

> Indeed, API output would be good. Also, how does Juju calculate/get the
> provider id? MAAS has no concept of a provider ID, so I'm not sure what
> you're talking about exactly.
>
> ** Changed in: maas
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1898195
>
> Title:
> Link layer device merge fails with "provider IDs not unique" on MAAS
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1898195/+subscriptions
>

Changed in juju:
status: New → Incomplete
Changed in juju:
milestone: 2.9-beta1 → 2.9-rc1
Changed in juju:
milestone: 2.9-rc1 → none
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for MAAS because there has been no activity for 60 days.]

Changed in maas:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers