[MAAS 2.8] KVM machines are created with Multiple NICs on the same space

[Peter Jose De Sousa]

Hi,

[Problem]

When provisioning Dynamic KVM machines on MAAS juju is creating the machines with 2+ NICs for each space - seemingly per relation/binding.

This causes charms to be configured incorrectly (machines communicating through an unexpected IP Address)

[Steps to reproduce]

Deploy maas 2.8.2 with two networks, oam-space and external-space

Provision baremetal nodes as KVM Pod machines, then deploy this bundle: http://paste.ubuntu.com/p/DZhJhvtd44/

Allow MAAS/Juju to provision the machines
Observe that machines come up with multiple NICs named after relations/bindings.

[Workaround]

Create MAAS KVM machines manually or with a script.

[Peter Jose De Sousa (pjds)]

Adding bootstrap logs in debug mode

[Peter Jose De Sousa (pjds)]

Adding Kubernetes deployment logs

[Peter Jose De Sousa (pjds)]

Picture of multiple NICs

[John A Meinel (jameinel)]

While the picture of multiple nics does show multiple nics, it doesn't quite have enough context to see what machines are assigned to what nic, etc. (For example, i would expect each container to get a nic, so are these multiple nics on a single container, or are they multiple nics across containers.)

This could be a bug about how we're interacting with MAAS, where we ask for multiple interfaces in a space, which on baremetal gets satisfied with a machine that has a single interface, but for MAAS's implementation of KVM servers will create multiple NICs instead. (eg, if we asked for foo=space-a, bar=space-a, then on baremetal that is satisfied by a single interface in space-a, and MAAS would return foo=ens1, bar=ens1, but for a KVM it creates ens1 in space-a and ens2 in space-a, and you get foo=ens1, bar=ens2.)

It would be good to see if MAAS is giving different results for baremetal machines vs KVM machines, and whether that was intentional on their part.

[Achilleas Anagnostopoulos (achilleasa)]

@pjds Trying to reproduce the bug. Which version of juju are you using?

[Peter Jose De Sousa (pjds)]

Hey Achilleas,

using 2.8.6-bionic-amd64

Thanks!

On Thu, Nov 5, 2020 at 4:00 PM Achilleas Anagnostopoulos <
<email address hidden>> wrote:

> @pjds Trying to reproduce the bug. Which version of juju are you using?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1902878
>
> Title:
> [MAAS 2.8] KVM machines are created with Multiple NICs on the same
> space
>
> Status in juju:
> New
>
> Bug description:
> Hi,
>
> [Problem]
>
> When provisioning Dynamic KVM machines on MAAS juju is creating the
> machines with 2+ NICs for each space - seemingly per relation/binding.
>
> This causes charms to be configured incorrectly (machines
> communicating through an unexpected IP Address)
>
> [Steps to reproduce]
>
> Deploy maas 2.8.2 with two networks, oam-space and external-space
>
> Provision baremetal nodes as KVM Pod machines, then deploy this
> bundle: http://paste.ubuntu.com/p/DZhJhvtd44/
>
> Allow MAAS/Juju to provision the machines
> Observe that machines come up with multiple NICs named after
> relations/bindings.
>
> [Workaround]
>
> Create MAAS KVM machines manually or with a script.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1902878/+subscriptions
>

--

[image: Description: Description: Description:
cid:image001.gif@01CA09E6.C3B72C10]
------------------------------

Peter De Sousa

Associate Field Software Engineer | Canonical Ltd.

*Mobile:* [phone] | *Email: **<email address hidden>
<email address hidden>*

[Pen Gale (pengale)]

I think this minimal bundle will reproduce the issue, if the issue is duplication in our request to MAAS when spinning things up on a KVM: https://paste.ubuntu.com/p/DQkCsWcz7w/

[Achilleas Anagnostopoulos (achilleasa)]

PR https://github.com/juju/juju/pull/12301 provides a fix for 2.8.