Comment 5 for bug 1806969

With MAAS 2.6.0 it does not work.

2019-07-01-22:33:22 root DEBUG maas root pod compose 2 hostname=vault-2 cores=4 memory=6144 storage=20.0 zone=3 interfaces=eth0:space=oam-space;eth1:space=internal-space
2019-07-01-22:33:27 root ERROR Command failed: pod compose 2 hostname=vault-2 cores=4 memory=6144 storage=20.0 zone=3 interfaces=''eth0:space=oam-space;eth1:space=internal-space''
2019-07-01-22:33:27 root ERROR b'Unable to compose machine because: Failed talking to pod: Unable to compose vault-2: error: Failed to start domain vault-2\nerror: error creating macvtap interface <email address hidden> (52:54:00:a0:82:36): Device or resource busy'
Traceback (most recent call last):
  File "/usr/local/bin/fce", line 11, in <module>
    load_entry_point('foundationcloudengine', 'console_scripts', 'fce')()
  File "/home/ubuntu/foundation/foundationcloudengine/foundationcloudengine/main.py", line 139, in entry_point
    sys.exit(main(sys.argv[1:]))
  File "/home/ubuntu/foundation/foundationcloudengine/foundationcloudengine/main.py", line 130, in main
    opts.func(opts)
  File "/home/ubuntu/foundation/foundationcloudengine/foundationcloudengine/build.py", line 65, in build_main
    args.steps)
  File "/home/ubuntu/foundation/foundationcloudengine/foundationcloudengine/build.py", line 44, in build_and_validate_if_needed
    layer.build_outer(only_steps)
  File "/home/ubuntu/foundation/foundationcloudengine/foundationcloudengine/layers/baselayer.py", line 118, in build_outer
    self.build(only_steps=only_steps)
  File "/home/ubuntu/foundation/foundationcloudengine/foundationcloudengine/layers/maaslayer.py", line 2310, in build
    super(MaasLayer, self).run_steps(only_steps)
  File "/home/ubuntu/foundation/foundationcloudengine/foundationcloudengine/layers/steppedbaselayer.py", line 51, in run_steps
    step.build()
  File "/home/ubuntu/foundation/foundationcloudengine/foundationcloudengine/layers/maaslayer.py", line 1294, in build
    zone['id'],
  File "/home/ubuntu/foundation/foundationcloudengine/foundationcloudengine/maas_cli.py", line 435, in add_pod_vm
    return cmd(maas_profile, command)
  File "/home/ubuntu/foundation/foundationcloudengine/foundationcloudengine/maas_cli.py", line 117, in cmd
    raise error
  File "/home/ubuntu/foundation/foundationcloudengine/foundationcloudengine/maas_cli.py", line 112, in cmd
    output = raw_cmd(maas_profile, split_command)
  File "/home/ubuntu/foundation/foundationcloudengine/foundationcloudengine/maas_cli.py", line 106, in raw_cmd
    return subprocess.check_output(maas_cmd)
  File "/usr/lib/python3.6/subprocess.py", line 356, in check_output
    **kwargs).stdout
  File "/usr/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['maas', 'root', 'pod', 'compose', '2', 'hostname=vault-2', 'cores=4', 'memory=6144', 'storage=20.0', 'zone=3', 'interfaces=eth0:space=oam-space;eth1:space=internal-space']' returned non-zero exit status 2.

This is a debug log from /var/log/libvirt/libvirt.log. In XML, there's bond1.1166 with type='direct' and mode='bridge'.

# infra-2 (Not OK)

2019-07-01 22:33:25.508+0000: 1992: debug : virDomainAttachDeviceFlags:8144 : dom=0x7fb488017ca0, (VM: name=vault-2, uuid=ebc61906-be64-4569-af47-46d159300fca), xml=<interface type='direct'>
  <source dev='bond1.1166' mode='bridge'/>
  <mac address='52:54:00:a0:82:36'/>
  <model type='virtio'/>
</interface>

For comparison, see the same log but from the other host, where creating KVM with 2 NICs succeeded. XML defines type='bridge'.

# infra-1 (OK)

2019-07-01 22:31:54.771+0000: 2063: debug : virDomainAttachDeviceFlags:8144 : dom=0x7f1490036d90, (VM: name=vault-1, uuid=4ac2c2c9-7774-422c-882e-cd5e7c127fec), xml=<interface type='bridge'>
   <source bridge='brinternal'/>
   <mac address='52:54:00:8e:40:c6'/>
   <model type='virtio'/>
</interface>

NICs on failing node:

ubuntu@infra-2:/var/log/libvirt$ ip -o l
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000\ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eno1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond1 state UP mode DEFAULT group default qlen 1000\ link/ether 4a:60:71:ea:74:de brd ff:ff:ff:ff:ff:ff
3: eno2: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond1 state UP mode DEFAULT group default qlen 1000\ link/ether 4a:60:71:ea:74:de brd ff:ff:ff:ff:ff:ff
4: eno3: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000\ link/ether a6:5e:e2:73:a4:63 brd ff:ff:ff:ff:ff:ff
5: eno4: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000\ link/ether a6:5e:e2:73:a4:63 brd ff:ff:ff:ff:ff:ff
6: broam: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000\ link/ether 86:37:a6:5e:04:a7 brd ff:ff:ff:ff:ff:ff
7: brinternal: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000\ link/ether 3e:7a:27:72:b1:b6 brd ff:ff:ff:ff:ff:ff
8: brexternal: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000\ link/ether 8a:cd:c0:86:80:b7 brd ff:ff:ff:ff:ff:ff
9: bond1: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000\ link/ether 4a:60:71:ea:74:de brd ff:ff:ff:ff:ff:ff
10: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue master broam state UP mode DEFAULT group default qlen 1000\ link/ether a6:5e:e2:73:a4:63 brd ff:ff:ff:ff:ff:ff
11: bond1.1166@bond1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master brinternal state UP mode DEFAULT group default qlen 1000\ link/ether 4a:60:71:ea:74:de brd ff:ff:ff:ff:ff:ff
12: bond1.1171@bond1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master brexternal state UP mode DEFAULT group default qlen 1000\ link/ether 4a:60:71:ea:74:de brd ff:ff:ff:ff:ff:ff