additional interfaces(eth1, eth2) did not come up automatically

Bug #1384333 reported by Nobuto Murata on 2014-10-22
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Wishlist
Unassigned
ceph (Juju Charms Collection)
Undecided
Unassigned

Bug Description

maas:
  Installed: 1.7.0~beta7+bzr3266-0ubuntu1~trusty1
juju-core:
  Installed: 1.20.10-0ubuntu1~14.04.1~juju1

ceph charm gave an error related to the fact that only one NIC is up and other 2 NIC missing "auto" stanza in /etc/network/interfaces, otherwise ceph charm cannot use those 2 interfaces and fails.

If maas is writing /etc/network/interfaces in maas nodes, maas should add "auto" stanza to all NICs available, not only for the first NIC.

[/etc/network/interfaces on g4vm04.maas]
==========
auto lo

auto eth0

source /etc/network/eth0.config

iface eth1 inet dhcp

iface eth2 inet dhcp
==========

ceph:
  series: trusty
  services:
    ceph:
      branch: lp:~openstack-charmers/charms/trusty/ceph/next
      constraints: tags=ceph
      num_units: 3
      options:
        fsid: '6547bd3e-1397-11e2-82e5-53567c8d32dc'
        monitor-secret: 'AQCXrnZQwI7KGBAAiPofmKEXKxu5bUzoYLVkbQ=='
        osd-devices: '/dev/vdb'
        osd-reformat: 'yes'
        ceph-cluster-network: '10.2.0.0/24'
        ceph-public-network: '10.3.0.0/24'

[NODE INFO]
    {
        "status": 6,
        "macaddress_set": [
            {
                "resource_uri": "/MAAS/api/1.0/nodes/node-93edd14e-5a05-11e4-aa61-525400cada8a/macs/52%3A54%3A00%3A9a%3Af2%3Aa2/",
                "mac_address": "52:54:00:9a:f2:a2"
            },
            {
                "resource_uri": "/MAAS/api/1.0/nodes/node-93edd14e-5a05-11e4-aa61-525400cada8a/macs/52%3A54%3A00%3A04%3Aea%3Abe/",
                "mac_address": "52:54:00:04:ea:be"
            },
            {
                "resource_uri": "/MAAS/api/1.0/nodes/node-93edd14e-5a05-11e4-aa61-525400cada8a/macs/52%3A54%3A00%3Ace%3A86%3A82/",
                "mac_address": "52:54:00:ce:86:82"
            }
        ],
        "cpu_count": 2,
        "zone": {
            "resource_uri": "/MAAS/api/1.0/zones/default/",
            "name": "default",
            "description": ""
        },
        "routers": [],
        "netboot": false,
        "osystem": "ubuntu",
        "storage": 1408,
        "hostname": "g4vm04.maas",
        "owner": "root",
        "ip_addresses": [
            "10.2.0.103",
            "10.3.0.103",
            "192.168.104.39"
        ],
        "system_id": "node-93edd14e-5a05-11e4-aa61-525400cada8a",
        "architecture": "amd64/generic",
        "memory": 2048,
        "power_type": "virsh",
        "tag_names": [
            "virtual",
            "ceph"
        ],
        "disable_ipv4": false,
        "distro_series": "trusty",
        "resource_uri": "/MAAS/api/1.0/nodes/node-93edd14e-5a05-11e4-aa61-525400cada8a/"
    },

[NETWORK INFO]
$ maas root node-group-interfaces list bbf11606-a893-46d0-a164-380910d7a7b1
[
    {
        "ip_range_high": null,
        "ip_range_low": null,
        "broadcast_ip": "10.230.127.255",
        "static_ip_range_low": null,
        "name": "eth0",
        "ip": "10.230.123.54",
        "subnet_mask": "255.255.248.0",
        "management": 0,
        "static_ip_range_high": null,
        "interface": "eth0"
    },
    {
        "ip_range_high": "192.168.104.200",
        "ip_range_low": "192.168.104.20",
        "broadcast_ip": "192.168.104.255",
        "static_ip_range_low": null,
        "name": "eth1",
        "ip": "192.168.104.10",
        "subnet_mask": "255.255.255.0",
        "management": 2,
        "static_ip_range_high": null,
        "interface": "eth1"
    },
    {
        "ip_range_high": "10.2.0.200",
        "ip_range_low": "10.2.0.100",
        "broadcast_ip": "10.2.0.255",
        "static_ip_range_low": null,
        "name": "ceph",
        "ip": "10.2.0.1",
        "subnet_mask": "255.255.255.0",
        "management": 1,
        "static_ip_range_high": null,
        "interface": "eth2"
    },
    {
        "ip_range_high": "10.3.0.200",
        "ip_range_low": "10.3.0.100",
        "broadcast_ip": "10.3.0.255",
        "static_ip_range_low": null,
        "name": "api",
        "ip": "10.3.0.1",
        "subnet_mask": "255.255.255.0",
        "management": 1,
        "static_ip_range_high": null,
        "interface": "eth3"
    }
]

Tags: cts Edit Tag help
Nobuto Murata (nobuto) on 2014-10-22
tags: added: cts
Blake Rouse (blake-rouse) wrote :

Can you give a good reason why all interfaces need to be brought up? If an extra interface is needed, why can't the charm bring up the interface?

Andres Rodriguez (andreserl) wrote :

This is expected behavior in 1.7. MAAS 1.8 or later will handle this different.

And not that if two or more interfaces are in the same network, and bonding is not configured, this means that we will have networking configuration issues.

Andres Rodriguez (andreserl) wrote :

Oh, and keep in mind that MAAS *never* bringed up other interfaces other than eth0.

Changed in maas:
status: New → Triaged
importance: Undecided → Wishlist
Nobuto Murata (nobuto) wrote :

ok, I'm not sure who should bring up additional interfaces then, adding a charm task here for now.

Nobuto Murata (nobuto) on 2014-10-22
description: updated
Nobuto Murata (nobuto) wrote :

If I understand it correctly, current MAAS marks only the PXE interface as automatic interface.

[./src/maasserver/networking_preseed.py]
def get_mac_for_automatic_interfaces(node):
    """Return the MAC addresses for `node` that should come up on boot.

    This will return the node's PXE MAC address as a normalized string.
    This is the MAC we expect the node to PXE boot from.

    :param node: A `Node`.
    :return: A normalised MAC address string.
    """
    pxe_mac = node.get_pxe_mac()
    return normalise_mac(unicode(pxe_mac.mac_address))

Blake Rouse (blake-rouse) wrote :

You are correct only the PXE interface is brought up. The other interfaces are configured but not set to auto.

James Page (james-page) on 2015-03-16
Changed in ceph (Juju Charms Collection):
status: New → Invalid
Blake Rouse (blake-rouse) wrote :

The new behavior in MAAS 1.9 is to bring up all interfaces and only the PXE interface will be configured statically. Unless you change the networking configuration which is now supported as well.

Changed in maas:
status: Triaged → Fix Committed
milestone: none → 1.9.0
Florian Haas (fghaas) wrote :

@blake-rouse, could you please point to the bzr commit that fixes this?

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