[2.4] MAAS doesn't notice change in interfaces

Bug #1761322 reported by Andres Rodriguez on 2018-04-04
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mike Pontillo

Bug Description

Before, my interfaces were managed in e/n/i. Now my interfaces are managed in /etc/netplan/netplan.yaml. However, MAAS doesn't get interfaces from either place.

Instead MAAS scans for interfaces differently, and MAAS rack controller doesn't update the reality of the interfaces.

Interfaces in the DB: http://paste.ubuntu.com/p/MgfpxqScKR/
Interfaces in ip addr sh:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether ec:a8:6b:fd:ac:70 brd ff:ff:ff:ff:ff:ff
    inet brd scope global eno1
       valid_lft forever preferred_lft forever
    inet6 fe80::eea8:6bff:fefd:ac70/64 scope link
       valid_lft forever preferred_lft forever
4: usb0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br0 state UP group default qlen 1000
    link/ether 00:0e:c6:88:b7:9f brd ff:ff:ff:ff:ff:ff
5: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether f2:a0:90:00:88:34 brd ff:ff:ff:ff:ff:ff
    inet brd scope global br0
       valid_lft forever preferred_lft forever
    inet6 fe80::f0a0:90ff:fe00:8834/64 scope link
       valid_lft forever preferred_lft forever
6: wlp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether c4:d9:87:5b:42:62 brd ff:ff:ff:ff:ff:ff

Interfaces with maas-rack support-dump:

Andres Rodriguez (andreserl) wrote :

FWIW I did this:

1. restart regiond
2. restart rackd

And the interfaces were never updated.

I rebooted the machine, and interfaces *were* updated.

Changed in maas:
milestone: none → 2.4.0beta2
importance: Undecided → Critical
assignee: nobody → Mike Pontillo (mpontillo)
status: New → Triaged
importance: Critical → High
Changed in maas:
milestone: 2.4.0beta2 → 2.4.0beta3
Mike Pontillo (mpontillo) wrote :

Can you please re-test this with Blake's fix to properly install the reactor? I think this was a symptom of "stalled reactor". When the service is properly running, we check the output of `ip addr` every 30 seconds and update the interfaces if there has been any change.

Changed in maas:
status: Triaged → Incomplete
Changed in maas:
milestone: 2.4.0beta3 → 2.4.0beta4
Changed in maas:
milestone: 2.4.0beta4 → 2.4.x
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers