Commissioning does not identify interface VLANs on secondary fabrics

Bug #1524924 reported by Narinder Gupta
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
High
Mike Pontillo
1.9
High
Mike Pontillo

Bug Description

install MAAS 1.9 with mutiple interfaces enabled and DHCP through MAAS on different subnet and fabrics.

Commission a node with mutiple interfaces but all attach to same fabric. During investigation found out that not all interfaces are enabled.

could init output http://paste.ubuntu.com/13900677/

commissioning output in MAAS
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 52:54:00:f5:af:4c brd ff:ff:ff:ff:ff:ff
    inet 10.4.1.70/21 brd 10.4.7.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::5054:ff:fef5:af4c/64 scope link
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 52:54:00:d2:df:db brd ff:ff:ff:ff:ff:ff
4: eth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 52:54:00:06:ff:71 brd ff:ff:ff:ff:ff:ff

but actual ip address after commisoning is as follows:

ubuntu@bootstrap:~$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 52:54:00:f5:af:4c brd ff:ff:ff:ff:ff:ff
    inet 10.4.1.70/21 brd 10.4.7.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::5054:ff:fef5:af4c/64 scope link
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 52:54:00:d2:df:db brd ff:ff:ff:ff:ff:ff
    inet 10.4.9.151/24 brd 10.4.9.255 scope global eth1
       valid_lft forever preferred_lft forever
    inet6 fe80::5054:ff:fed2:dfdb/64 scope link
       valid_lft forever preferred_lft forever
4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 52:54:00:06:ff:71 brd ff:ff:ff:ff:ff:ff
    inet 10.2.66.151/24 brd 10.2.66.255 scope global eth2
       valid_lft forever preferred_lft forever
    inet6 fe80::5054:ff:fe06:ff71/64 scope link
       valid_lft forever preferred_lft forever
ubuntu@bootstrap:~$

Related branches

Revision history for this message
Andres Rodriguez (andreserl) wrote :

Hi Narinder,

After the machine has fully commissioned, can you do:

dhclient eth2 ?

If eth2 obtains an IP address for a subnet that's on a different fabric, this will be udpated. If there's no IP address obtained from DHCP, then the interface will be added to the same fabric as the PXE interface.

Changed in maas:
status: New → Incomplete
Revision history for this message
Andres Rodriguez (andreserl) wrote :

Also, can you pelase list all your fabrics/subnets ?

Revision history for this message
Narinder Gupta (narindergupta) wrote :
Download full text (3.9 KiB)

ubuntu@bootstrap:~$ sudo dhclient eth2
RTNETLINK answers: File exists
ubuntu@bootstrap:~$

ubuntu@node1:~$ ssh 10.4.1.70
Welcome to Ubuntu 14.04.1 LTS (GNU/Linux 3.13.0-35-generic x86_64)

 * Documentation: https://help.ubuntu.com/

  System information as of Thu Dec 10 17:51:20 UTC 2015

  System load: 0.03 Users logged in: 0
  Usage of /home: unknown IP address for eth0: 10.4.1.70
  Memory usage: 2% IP address for eth1: 10.4.9.151
  Swap usage: 0% IP address for eth2: 10.2.66.151
  Processes: 111

  Graph this data and manage this system at:
    https://landscape.canonical.com/

  Get cloud support with Ubuntu Advantage Cloud Guest:
    http://www.ubuntu.com/business/services/cloud

tmpfs-root /media/root-rw tmpfs rw,relatime 0 0
overlayroot / overlayfs rw,relatime,lowerdir=/media/root-ro,upperdir=/media/root-rw//overlay 0 0
/dev/disk/by-path/ip-10.4.1.2:3260-iscsi-iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-amd64-generic-trusty-release-lun-1 /media/root-ro ext4 ro,relatime,data=ordered 0 0

Last login: Thu Dec 10 17:51:20 2015 from 10.4.1.1
ubuntu@bootstrap:~$

ubuntu@node1:~$ maas maas fabrics read
Success.
Machine-readable output follows:
[
    {
        "resource_uri": "/MAAS/api/1.0/fabrics/0/",
        "vlans": [
            {
                "name": "untagged",
                "vid": 0,
                "mtu": 1500,
                "fabric": "fabric-0",
                "id": 0,
                "resource_uri": "/MAAS/api/1.0/vlans/0/"
            }
        ],
        "class_type": null,
        "name": "fabric-0",
        "id": 0
    },
    {
        "resource_uri": "/MAAS/api/1.0/fabrics/1/",
        "vlans": [
            {
                "name": "untagged",
                "vid": 0,
                "mtu": 1500,
                "fabric": "fabric-1",
                "id": 5001,
                "resource_uri": "/MAAS/api/1.0/vlans/5001/"
            }
        ],
        "class_type": null,
        "name": "fabric-1",
        "id": 1
    },
    {
        "resource_uri": "/MAAS/api/1.0/fabrics/2/",
        "vlans": [
            {
                "name": "untagged",
                "vid": 0,
                "mtu": 1500,
                "fabric": "fabric-2",
                "id": 5002,
                "resource_uri": "/MAAS/api/1.0/vlans/5002/"
            }
        ],
        "class_type": null,
        "name": "fabric-2",
        "id": 2
    }
]
ubuntu@node1:~$

ubuntu@node1:~$ maas maas subnets read
Success.
Machine-readable output follows:
[
    {
        "dns_servers": [],
        "name": "10.4.0.0/21",
        "space": "space-0",
        "vlan": {
            "name": "untagged",
            "vid": 0,
            "mtu": 1500,
            "fabric": "fabric-0",
            "id": 0,
            "resource_uri": "/MAAS/api/1.0/vlans/0/"
        },
        "gateway_ip": "10.4.0.1",
        "cidr": "10.4.0.0/21",
        "id": 1,
        "resource_uri": "/MAAS/api/1.0/subnets/1/"
    },
    {
        "dns_servers": [],
        "name": "10.4.9.0/24",
        "space": "space-0",
        "vlan": {
            "name": "untagged",
            "vid": 0, ...

Read more...

Changed in maas:
status: Incomplete → New
Revision history for this message
Narinder Gupta (narindergupta) wrote :

all information provided and moving to new queue.

Revision history for this message
Narinder Gupta (narindergupta) wrote : Re: [Bug 1524924] Re: maas does not enable all interfaces during commisoning
Download full text (3.7 KiB)

updated the bug with all information needed.

Thanks and Regards,
Narinder Gupta (PMP) <email address hidden>
Canonical, Ltd. narindergupta [irc.freenode.net]
+1.281.736.5150 narindergupta2007[skype]

Ubuntu- Linux for human beings | www.ubuntu.com | www.canonical.com

On Thu, Dec 10, 2015 at 12:37 PM, Andres Rodriguez <email address hidden>
wrote:

> Also, can you pelase list all your fabrics/subnets ?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1524924
>
> Title:
> maas does not enable all interfaces during commisoning
>
> Status in MAAS:
> Incomplete
>
> Bug description:
> install MAAS 1.9 with mutiple interfaces enabled and DHCP through MAAS
> on different subnet and fabrics.
>
> Commission a node with mutiple interfaces but all attach to same
> fabric. During investigation found out that not all interfaces are
> enabled.
>
> could init output http://paste.ubuntu.com/13900677/
>
> commissioning output in MAAS
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
> group default
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 scope host lo
> valid_lft forever preferred_lft forever
> inet6 ::1/128 scope host
> valid_lft forever preferred_lft forever
> 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
> state UP group default qlen 1000
> link/ether 52:54:00:f5:af:4c brd ff:ff:ff:ff:ff:ff
> inet 10.4.1.70/21 brd 10.4.7.255 scope global eth0
> valid_lft forever preferred_lft forever
> inet6 fe80::5054:ff:fef5:af4c/64 scope link
> valid_lft forever preferred_lft forever
> 3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group
> default qlen 1000
> link/ether 52:54:00:d2:df:db brd ff:ff:ff:ff:ff:ff
> 4: eth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group
> default qlen 1000
> link/ether 52:54:00:06:ff:71 brd ff:ff:ff:ff:ff:ff
>
> but actual ip address after commisoning is as follows:
>
> ubuntu@bootstrap:~$ ip addr
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
> group default
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 scope host lo
> valid_lft forever preferred_lft forever
> inet6 ::1/128 scope host
> valid_lft forever preferred_lft forever
> 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
> state UP group default qlen 1000
> link/ether 52:54:00:f5:af:4c brd ff:ff:ff:ff:ff:ff
> inet 10.4.1.70/21 brd 10.4.7.255 scope global eth0
> valid_lft forever preferred_lft forever
> inet6 fe80::5054:ff:fef5:af4c/64 scope link
> valid_lft forever preferred_lft forever
> 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
> state UP group default qlen 1000
> link/ether 52:54:00:d2:df:db brd ff:ff:ff:ff:ff:ff
> inet 10.4.9.151/24 brd 10.4.9.255 scope global eth1
> valid_lft forever preferred_lft forever
> inet6 f...

Read more...

summary: - maas does not enable all interfaces during commisoning
+ Commissioning does not resolve interface VLANs on secondary fabrics
summary: - Commissioning does not resolve interface VLANs on secondary fabrics
+ Commissioning does not identify interface VLANs on secondary fabrics
Changed in maas:
milestone: none → next
importance: Undecided → Critical
importance: Critical → High
assignee: nobody → Mike Pontillo (mpontillo)
status: New → Triaged
Changed in maas:
status: Triaged → Fix Committed
Changed in maas:
status: Fix Committed → Fix Released
milestone: next → none
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers