[2.0a1] PXE interface incorrectly displayed on the UI

Bug #1556366 reported by Andres Rodriguez on 2016-03-12
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
High
LaMont Jones

Bug Description

The PXE interface is incorrectly determine. In this case, eth0 is the PXE interface but MAAS is saying eth1: is:

http://people.canonical.com/~andreserl/pxe-interface.png

Interface shows that the PXE MAC is eth1, but the API shows it is eth0.
http://people.canonical.com/~andreserl/interface_mac_pxe.png

Also, after taking a close look at the API output:

1. Fabric on eth0 is determined incorrectly, as this should be 'Fabric-2' instead of 'Fabric-0'. This reflects on both the API and UI.
2. PXE interface is determined correctly on the API, but what the Web UI shows is different.

Machine's output:

[
    {
        "type": "physical",
        "id": 136,
        "resource_uri": "/MAAS/api/2.0/nodes/4y3haq/interfaces/136/",
        "children": [],
        "mac_address": "74:d4:35:89:bd:2b",
        "params": "",
        "vlan": {
            "primary_rack": null,
            "id": 1,
            "resource_uri": "/MAAS/api/2.0/vlans/1/",
            "mtu": 1500,
            "name": "untagged",
            "dhcp_on": false,
            "secondary_rack": null,
            "fabric": "fabric-0",
            "vid": 0
        },
        "tags": [],
        "parents": [],
        "effective_mtu": 1500,
        "enabled": true,
        "name": "eth0",
        "links": [],
        "discovered": null
    },
    {
        "type": "physical",
        "id": 137,
        "resource_uri": "/MAAS/api/2.0/nodes/4y3haq/interfaces/137/",
        "children": [],
        "mac_address": "74:d4:35:89:bd:2c",
        "params": "",
        "vlan": {
            "primary_rack": null,
            "id": 1,
            "resource_uri": "/MAAS/api/2.0/vlans/1/",
            "mtu": 1500,
            "name": "untagged",
            "dhcp_on": false,
            "secondary_rack": null,
            "fabric": "fabric-0",
            "vid": 0
        },
        "tags": [],
        "parents": [],
        "effective_mtu": 1500,
        "enabled": true,
        "name": "eth1",
        "links": [],
        "discovered": null
    }
]

VLAN output:

ubuntu@trusty-maas9:~$ maas admin vlans read fabric-0
Success.
Machine-readable output follows:
[
    {
        "vid": 0,
        "resource_uri": "/MAAS/api/2.0/vlans/1/",
        "secondary_rack": null,
        "id": 1,
        "fabric": "fabric-0",
        "mtu": 1500,
        "name": "untagged",
        "primary_rack": null,
        "dhcp_on": false
    }
]
ubuntu@trusty-maas9:~$ maas admin vlans read fabric-1
Success.
Machine-readable output follows:
[
    {
        "vid": 0,
        "resource_uri": "/MAAS/api/2.0/vlans/2/",
        "secondary_rack": null,
        "id": 2,
        "fabric": "fabric-1",
        "mtu": 1500,
        "name": "untagged",
        "primary_rack": null,
        "dhcp_on": false
    }
]
ubuntu@trusty-maas9:~$ maas admin vlans read fabric-2
Success.
Machine-readable output follows:
[
    {
        "vid": 0,
        "resource_uri": "/MAAS/api/2.0/vlans/3/",
        "secondary_rack": null,
        "id": 3,
        "fabric": "fabric-2",
        "mtu": 1500,
        "name": "untagged",
        "primary_rack": "4y3h7n",
        "dhcp_on": true
    }
]

Related branches

Changed in maas:
milestone: none → 2.0.0
summary: - Fabric are incorrectly determined on enlistment, which may cause PXE
- interface incorrectly showed in the UI
+ [2.0a1] PXE interface incorrectly displayed on the UI
Changed in maas:
importance: Undecided → High
status: New → Triaged
Changed in maas:
assignee: nobody → LaMont Jones (lamont)
Changed in maas:
status: Triaged → Fix Committed
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers