MAAS bridge script does not explicitly parse new alias syntax in MAAS 2.1

Bug #1646473 reported by Andrew McDermott
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
Low
Unassigned

Bug Description

Using MAAS 2.1 (and curtin 0.1.0~bzr425-0ubuntu1~16.04.1) I notice the format of aliases has changed from using ':' as a indicator to repeating the 'iface' stanza - which is a perfectly reasonable thing to do.

However, Juju's MAAS bridging script was reliant on the old format.

An example alias now looks like:

auto ens3
iface ens3 inet static
  address 192.168.20.68/24
  gateway 192.168.20.2
  mtu 1500

# control-alias ens3
iface ens3 inet static
  address 192.168.20.69/24

We previously got 'ens3:1' for the alias and the bridge script looked for and parsed that syntax explicitly. When we run the script against the new format we now get:

auto ens3
iface ens3 inet manual
  mtu 1500

auto br-ens3
  iface br-ens3 inet static
  address 192.168.20.68/24
  gateway 192.168.20.2
  bridge_ports ens3

auto ens3
  iface ens3 inet manual

auto br-ens3
  iface br-ens3 inet static
  address 192.168.20.69/24
  bridge_ports ens3

which appears to work, though this is a sample size of 1.

For the moment this bug is raised for awareness of the change in format.

Looking on a machine I see the following:

$ brctl show bridge name bridge id STP enabled interfaces br-ens3 8000.525400ccead9 no ens3 br-ens4 8000.5254004b7d91 no ens4 lxdbr0 8000.000000000000 no

$ ip addr show br-ens3 | grep -w inet
                                                                                             inet 192.168.20.68/24 brd 192.168.20.255 scope global br-ens3 inet 192.168.20.69/24 brd 192.168.20.255 scope global secondary br-ens3

description: updated
Changed in juju:
status: New → Triaged
importance: Undecided → High
milestone: none → 2.2.0
Revision history for this message
Andrew McDermott (frobware) wrote :

We have a similar[1] alias bug which may no longer need fixing in light of the curtin changes identified by this bug. This needs some investigation to understand where/when curtin version (0.1.0~bzr425-0ubuntu1~16.04.1) gets backported to.

[1] https://bugs.launchpad.net/juju/+bug/1631940

Curtis Hovey (sinzui)
Changed in juju:
milestone: 2.2-beta1 → 2.2-beta2
Curtis Hovey (sinzui)
Changed in juju:
milestone: 2.2-beta2 → 2.2-beta3
Changed in juju:
milestone: 2.2-beta3 → 2.2-beta4
Changed in juju:
milestone: 2.2-beta4 → 2.2-rc1
Tim Penhey (thumper)
Changed in juju:
importance: High → Medium
milestone: 2.2-rc1 → none
Ian Booth (wallyworld)
tags: removed: maas
Revision history for this message
Canonical Juju QA Bot (juju-qa-bot) wrote :

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.

Changed in juju:
importance: Medium → Low
tags: added: expirebugs-bot
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.