Juju fails to launch containers when netplan includes bridge and vlan configuration

Bug #1777717 reported by Josh Kirkpatrick
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Incomplete
High
Unassigned

Bug Description

I read bug #1771120 and I had a similar issue. I installed juju --beta and still having the unmarshal errors.

jluczani@us-a-reg-maas:~/openstack-base$ juju --version
2.4-rc2-xenial-amd64

However, this only happens when I attempt to deploy hosts running ubuntu bionic. No errors on exact same deployment on Xenial.

Machine State DNS Inst id Series AZ Message
0 started x.x.x.2 kgs3fe bionic us-a-001 Deployed
0/lxd/0 down pending bionic bridge activation error: yaml: unmarshal errors:
  line 7: field bonds not found in struct netplan.Network
  line 7: field vlans not found in struct netplan.Network
0/lxd/1 down pending bionic bridge activation error: yaml: unmarshal errors:
  line 7: field bonds not found in struct netplan.Network
  line 7: field vlans not found in struct netplan.Network
1 started 10.76.83.99 pyqshy bionic us-a-001 Deployed
1/lxd/0 down pending bionic bridge activation error: yaml: unmarshal errors:
  line 7: field bonds not found in struct netplan.Network
  line 7: field vlans not found in struct netplan.Network
1/lxd/1 down pending bionic bridge activation error: yaml: unmarshal errors:
  line 7: field bonds not found in struct netplan.Network
  line 7: field vlans not found in struct netplan.Network
1/lxd/2 down pending bionic bridge activation error: yaml: unmarshal errors:
  line 7: field bonds not found in struct netplan.Network
  line 7: field vlans not found in struct netplan.Network
1/lxd/3 down pending bionic bridge activation error: yaml: unmarshal errors:
  line 7: field bonds not found in struct netplan.Network
  line 7: field vlans not found in struct netplan.Network
2 started 10.76.83.103 477rb4 bionic us-a-001 Deployed
2/lxd/0 down pending bionic bridge activation error: yaml: unmarshal errors:
  line 7: field bonds not found in struct netplan.Network
  line 7: field vlans not found in struct netplan.Network
2/lxd/1 down pending bionic bridge activation error: yaml: unmarshal errors:
  line 7: field bonds not found in struct netplan.Network
  line 7: field vlans not found in struct netplan.Network
2/lxd/2 down pending bionic bridge activation error: yaml: unmarshal errors:
  line 7: field bonds not found in struct netplan.Network
  line 7: field vlans not found in struct netplan.Network
3 started 10.76.83.101 qnge73 bionic us-a-001 Deployed

Tags: juju
description: updated
Revision history for this message
John A Meinel (jameinel) wrote : Re: [Bug 1777717] [NEW] Juju fails to launch containers when netplan includes bridge and vlan configuration
Download full text (7.8 KiB)

I see that your client is juju-2.4rc2 can you confirm that "juju status -m
controller" lists 2.4rc2 on the controller as well? We certainly landed
code into the 2.4 series (and late 2.3 series) to explicitly handle bonds
and vlans. And looking at the code I still see it there.

Are you running against a controller that wasn't upgraded? It isn't
sufficient to upgrade the client, the bug is in the server code.

2.3.8 should also have the updated code, so you shouldn't have to upgrade
to 2.4rc2 for this.

If you *are* hitting this and are sure that everything is 2.4 we definitely
need to investigate, as it would seem the fix for bug #1771120 somehow
regressed. (I see the correct code in the 2.4 branch, but we need to
understand you would be having problems.)

John
=:->

On Tue, Jun 19, 2018 at 11:33 PM, Josh Kirkpatrick <
<email address hidden>> wrote:

> Public bug reported:
>
> I read bug #1771120 and I had a similar issue. I installed juju --beta
> and still having the unmarshal errors.
>
> jluczani@us-a-reg-maas:~/openstack-base$ juju --version
> 2.4-rc2-xenial-amd64
>
>
> However, this only happens when I attempt to deploy hosts running ubuntu
> bionic. No errors on exact same deployment on Xenial.
>
> Machine State DNS Inst id Series AZ Message
> 0 started x.x.x.2 kgs3fe bionic us-a-001 Deployed
> 0/lxd/0 down pending bionic bridge
> activation error: yaml: unmarshal errors:
> line 7: field bonds not found in struct netplan.Network
> line 7: field vlans not found in struct netplan.Network
> 0/lxd/1 down pending bionic bridge activation error: yaml:
> unmarshal errors:
> line 7: field bonds not found in struct netplan.Network
> line 7: field vlans not found in struct netplan.Network
> 1 started 10.76.83.99 pyqshy bionic us-a-001 Deployed
> 1/lxd/0 down pending bionic bridge
> activation error: yaml: unmarshal errors:
> line 7: field bonds not found in struct netplan.Network
> line 7: field vlans not found in struct netplan.Network
> 1/lxd/1 down pending bionic bridge activation error: yaml:
> unmarshal errors:
> line 7: field bonds not found in struct netplan.Network
> line 7: field vlans not found in struct netplan.Network
> 1/lxd/2 down pending bionic bridge activation error: yaml:
> unmarshal errors:
> line 7: field bonds not found in struct netplan.Network
> line 7: field vlans not found in struct netplan.Network
> 1/lxd/3 down pending bionic bridge activation error: yaml:
> unmarshal errors:
> line 7: field bonds not found in struct netplan.Network
> line 7: field vlans not found in struct netplan.Network
> 2 started 10.76.83.103 477rb4 bionic us-a-001 Deployed
> 2/lxd/0 down pending bionic bridge
> activation error: yaml: unmarshal errors:
> line 7: field bonds not found in struct netplan.Network
> line 7: field vlans not found in struct netplan.Network
> 2/lxd/1 down pending bionic bridge activation error: yaml:
> unmarshal errors:
> line 7: field bonds not found in struct netplan.Network
> line 7: field v...

Read more...

Changed in juju:
status: New → Incomplete
importance: Undecided → High
Revision history for this message
Josh Kirkpatrick (rockfreak101) wrote :

Yes, that is it. Controller is not updated. Very sorry, forgot. May close.

jluczani@us-a-reg-maas:~/openstack-base$ juju status -m controller
Model Controller Cloud/Region Version SLA Notes
controller juju us-a-reg-maas 2.3.7 unsupported upgrade available: 2.3.8

Machine State DNS Inst id Series AZ Message
0 started 10.76.83.117 atk376 xenial default Deployed

Revision history for this message
Josh Kirkpatrick (rockfreak101) wrote :

jluczani@us-a-reg-maas:~/openstack-base$ juju upgrade-juju
best version:
    2.3.8
started upgrade to 2.3.8
jluczani@us-a-reg-maas:~/openstack-base$ juju status -m controller
Model Controller Cloud/Region Version SLA
controller juju us-a-reg-maas 2.3.8 unsupported

Machine State DNS Inst id Series AZ Message
0 started 10.76.83.117 atk376 xenial default Deployed

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.