Bridge to vlan not working when deploying with Ubuntu 16.04

Bug #1835652 reported by Wojtek Rakoniewski on 2019-07-07
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Undecided
Unassigned

Bug Description

I have configured machine with following network scenario:
- changed physical ethernet interface name to "phos"
- "phos" has unconfigured ip address
- add vlans 3111, 3112 and 3161 to interface "phos"
- add bridges:
  phosinternal do vlan 3111
  phvmpublic to vlan 3161
  phvmtunnel to vlan 3112
- add ip addresses to phosinternal and phvmtunnel
(network configuration screenshot is attached)

I deployed machine with Ubuntu 16.04, but network after deploy on the machine is not configured properly with following problems:
- there is no bridge interfaces configured in /etc/network/interfaces.d/50-cloud-init.cfg
- interfaces without ip address have no "auto <ifname>" section
Please see content of /etc/network/interfaces.d/50-cloud-init.cfg at the end of message.

I used previously MAAS 2.5.2 and everything worked properly, problem appeared after MAAS upgrade to 2.6.0 (7802-g59416a869-0ubuntu1~18.04.1)

I also checked deploying the same on Ubuntu 18.04 with netplan and it works correctly.

/etc/network/interfaces.d/50-cloud-init.cfg:

auto phcephpublic
iface phcephpublic inet static
    address 10.48.70.2/20
    dns-nameservers 10.48.144.30
    dns-search os-op infra maas os-ka os-main storage
    mtu 9000

auto phdeploy
iface phdeploy inet static
    address 10.48.146.2/20
    dns-nameservers 10.48.144.30
    dns-search os-op infra maas os-ka os-main storage
    gateway 10.48.144.1
    mtu 1500
    post-up route add -net 10.48.255.40/31 gw 10.48.144.40 || true
    pre-down route del -net 10.48.255.40/31 gw 10.48.144.40 || true

iface phos inet manual
    mtu 9100

auto phosinternal
iface phosinternal inet static
    address 10.48.25.2/20
    dns-nameservers 10.48.144.30
    dns-search os-op infra maas os-ka os-main storage
    bridge_fd 15
    bridge_ports phos.3111
    bridge_stp off

iface phvmpublic inet manual
    bridge_fd 15
    bridge_ports phos.3161
    bridge_stp off

auto phvmtunnel
iface phvmtunnel inet static
    address 10.48.41.2/20
    dns-nameservers 10.48.144.30
    dns-search os-op infra maas os-ka os-main storage
    bridge_fd 15
    bridge_ports phos.3112
    bridge_stp off

iface phos.3111 inet manual
    vlan-raw-device phos
    vlan_id 3111

iface phos.3112 inet manual
    vlan-raw-device phos
    vlan_id 3112

iface phos.3161 inet manual
    vlan-raw-device phos
    vlan_id 3161

Ebbex (eb4x) wrote :

It looks like it's right there in the config;

iface phvmpublic inet manual
    bridge_fd 15
    bridge_ports phos.3161
    bridge_stp off

That's what it looks like when you don't give a bridge an ip address. (according to your screenshot)

Are you sure that's your problem?

Ebbex (eb4x) wrote :

Ah, nevermind I misread a bit. You're seeing the same or similar issues as me #1834751

Wojtek Rakoniewski (enter2608) wrote :

Yes, not working bridge it can be the same as #1834751. Bridge exist in config file - my mistake.
"auto <ifname>" still is a problem - there is no line for interfaces without IP address.

Ebbex (eb4x) wrote :

As a workaround you can try

maas {profile} maas set-config name=force_v1_network_yaml value=true

from the cli.

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

Other bug subscribers