Multi interface issue while charm deployed on centos image

[Rajesh Kumar Chaturvedi]

Setup Details:

juju version
2.0-beta16-xenial-amd64

Maas Version
MAAS Version 2.0.0+bzr5189-0ubuntu1 (16.04.1)

Bootstrap OS:
trusty (hwe-t)

Deployed Image used:-
Kernel version:--
Linux 3.10.0-327.36.3.el7.x86_64 x86_64

OS version:--
CentOS Linux release 7.2.1511 (Core)

Issue Reported:--
The charm deployed node(Centos) comes with only one NIC (i.e. management plane ip) as shown below
http://paste.ubuntu.com/23567805/

But using same setup using Ubuntu as an image, charms are getting deployed with proper number of NIC cards as expected.

The MAAS interface configured for deploying charm on node using centos image is as shown below:
http://pasteboard.co/35ahhAVj.jpg

[Anastasia (anastasia-macmood)]

You are using a beta version. Could you please try later version of either Juju 2.0.x or 2.1.x?

[Andrew McDermott (frobware)]

We currently have this bug on non-ubuntu systems when bridging interfaces:

  https://bugs.launchpad.net/juju/+bug/1535678

[Curtis Hovey (sinzui)]

I suspect a maas issue since maas is resonsible for starting the machine and installing the OS. The network set up by maas (with the aid of curtain). Juju does not create eth* devices We do test centos with 1 nick in aws

I happen to know that the maas centos images are created by CPC from generic centos images. CPC does not change the image, so maas might not know how to add more than one nic.

[Andres Rodriguez (andreserl)]

MAAS doesn't currently support multiple interface configuration for CentOS. Marking this as won't fix.