Canonical Juju

  1. Bug #1733592
  2. Comment #5

Comment 5 for bug 1733592

Revision history for this message
Ante Karamatić (ivoks) wrote :

New data shows that MAAS had a space and vlan defined with MTU 1500:

    {
        "id": 3,
        "name": "internal-space",
        "subnets": [
            {
                "gateway_ip": null,
                "dns_servers": [],
                "resource_uri": "/MAAS/api/2.0/subnets/3/",
                "active_discovery": false,
                "managed": true,
                "id": 3,
                "allow_proxy": true,
                "vlan": {
                    "mtu": 1500,
                    "fabric": "default",
                    "relay_vlan": null,
                    "resource_uri": "/MAAS/api/2.0/vlans/5033/",
                    "primary_rack": null,
                    "external_dhcp": null,
                    "id": 5033,
                    "fabric_id": 30,
                    "name": "",
                    "dhcp_on": false,
                    "vid": 2733,
                    "space": "internal-space",
                    "secondary_rack": null
                },
                "name": "internal",
                "cidr": "192.168.33.0/24",
                "rdns_mode": 2,
                "space": "internal-space"
            }
        ],
        "vlans": [
            {
                "mtu": 1500,
                "fabric": "default",
                "relay_vlan": null,
                "resource_uri": "/MAAS/api/2.0/vlans/5033/",
                "primary_rack": null,
                "external_dhcp": null,
                "id": 5033,
                "fabric_id": 30,
                "name": "",
                "dhcp_on": false,
                "vid": 2733,
                "space": "internal-space",
                "secondary_rack": null
            }
        ],
        "resource_uri": "/MAAS/api/2.0/spaces/3/"
    },

When one tries to attach an interface to that VLAN, with MTU 9000, it should have raised an issue. Instead, MAAS happily connected two layer 2 objects (VLAN and a NIC) with different MTU values:

            {
                "mac_address": "5c:b9:01:9b:58:a9",
                "params": {
                    "mtu": 9000
                },
                "id": 109,
                "vlan": {
                    "fabric_id": 30,
                    "fabric": "default",
                    "mtu": 1500,
                    "relay_vlan": null,
                    "primary_rack": "abcfkh",
                    "resource_uri": "/MAAS/api/2.0/vlans/5031/",
                    "secondary_rack": "cmkt8t",
                    "name": "untagged",
                    "vid": 0,
                    "dhcp_on": true,
                    "id": 5031,
                    "space": "oam-space",
                    "external_dhcp": null
                },
                "type": "physical",
                "links": [],
                "system_id": "wn67a6",
                "enabled": true,
                "parents": [],
                "name": "eth1",
                "resource_uri": "/MAAS/api/2.0/nodes/wn67a6/interfaces/109/",
                "discovered": null,
                "tags": [
                    "sriov"
                ],
                "effective_mtu": 9000,
                "children": [
                    "eth1.2733",
                    "eth1.2734"
                ]
            },

Is this expected behavior in MAAS?