VMWare provider container networking not working

[Merlijn Sebrechts]

# What I did

1. In VMWare, set "promiscuous mode", "MAC address changes" and "forged transmits" to "allowed" on the virtual switches.
2. setup a controller on vmware with container-networking=provider
3. create container

# Result

Container is not accessible.

ifconfig output: http://paste.ubuntu.com/26417310/

It does seem as if the bridge is added correctly:

```
bridge name bridge id STP enabled interfaces
br-ens192 8000.005056a41506 no ens192
       vethB20SMK
lxdbr0 8000.000000000000 no
```

+---------------------+---------+------+------+------------+-----------+
| NAME | STATE | IPV4 | IPV6 | TYPE | SNAPSHOTS |
+---------------------+---------+------+------+------------+-----------+
| juju-f87094-0-lxd-0 | RUNNING | | | PERSISTENT | 0 |
+---------------------+---------+------+------+------------+-----------+

full systemd log from that unit: http://paste.ubuntu.com/26417363/

# Original discussion

- https://bugs.launchpad.net/juju/+bug/1733882

(this is case #5)

[John A Meinel (jameinel)]

I presume that you did have DHCP running on the network that ens192 was connected to (presumably that was how ens192 got the 10.10.137.58 that we ended up assigning to br-ens192).

Can you go into the container and grab a copy of /etc/network/interfaces
We would expect that eth0 should be configured as DHCP, but its possible we did something wrong and it would be configured as "manual", but no actual IP was assigned.

[Merlijn Sebrechts (merlijn-sebrechts)]

Yes, DHCP is running on the network ens192 was connected to.

This is /etc/network/interfaces of the container.

auto lo eth0

iface lo inet loopback
  dns-nameservers 10.10.139.95
  dns-search tenguvmware

iface eth0 inet dhcp

In the logs of the container:

cat /var/log/syslog | grep dhc
Apr 13 12:08:21 juju-429b3e-0-lxd-0 dhclient[297]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 (xid=0x6202a84f)
Apr 13 12:08:24 juju-429b3e-0-lxd-0 dhclient[297]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8 (xid=0x6202a84f)
Apr 13 12:08:32 juju-429b3e-0-lxd-0 dhclient[297]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10 (xid=0x6202a84f)
Apr 13 12:08:42 juju-429b3e-0-lxd-0 dhclient[297]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15 (xid=0x6202a84f)
Apr 13 12:08:57 juju-429b3e-0-lxd-0 dhclient[297]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11 (xid=0x6202a84f)
Apr 13 12:09:08 juju-429b3e-0-lxd-0 dhclient[297]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12 (xid=0x6202a84f)
Apr 13 12:09:20 juju-429b3e-0-lxd-0 dhclient[297]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12 (xid=0x6202a84f)
Apr 13 12:09:32 juju-429b3e-0-lxd-0 dhclient[297]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12 (xid=0x6202a84f)
Apr 13 12:09:44 juju-429b3e-0-lxd-0 dhclient[297]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10 (xid=0x6202a84f)
Apr 13 12:09:54 juju-429b3e-0-lxd-0 dhclient[297]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11 (xid=0x6202a84f)
Apr 13 12:10:05 juju-429b3e-0-lxd-0 dhclient[297]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8 (xid=0x6202a84f)
Apr 13 12:10:13 juju-429b3e-0-lxd-0 dhclient[297]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11 (xid=0x6202a84f)
Apr 13 12:10:24 juju-429b3e-0-lxd-0 dhclient[297]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 (xid=0x6202a84f)
Apr 13 12:10:31 juju-429b3e-0-lxd-0 dhclient[297]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 (xid=0x6202a84f)
Apr 13 12:10:38 juju-429b3e-0-lxd-0 dhclient[297]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11 (xid=0x6202a84f)
Apr 13 12:10:49 juju-429b3e-0-lxd-0 dhclient[297]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 18 (xid=0x6202a84f)
Apr 13 12:11:07 juju-429b3e-0-lxd-0 dhclient[297]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12 (xid=0x6202a84f)
Apr 13 12:11:19 juju-429b3e-0-lxd-0 dhclient[297]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15 (xid=0x6202a84f)
Apr 13 12:11:34 juju-429b3e-0-lxd-0 dhclient[297]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 (xid=0x6202a84f)
Apr 13 12:11:41 juju-429b3e-0-lxd-0 dhclient[297]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9 (xid=0x6202a84f)
Apr 13 12:11:50 juju-429b3e-0-lxd-0 dhclient[297]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11 (xid=0x6202a84f)
Apr 13 12:12:01 juju-429b3e-0-lxd-0 dhclient[297]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13 (xid=0x6202a84f)
Apr 13 12:12:14 juju-429b3e-0-lxd-0 dhclient[297]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67...

[Merlijn Sebrechts (merlijn-sebrechts)]

*note that the dhcp server is also a juju-provisioned VM with the same network setup as the host.

[Pen Gale (pengale)]

This is on our list of priorities for Juju 2.9, pending the setup of our VMWare cluster so that we can do internal testing of the fix.

[Pen Gale (pengale)]

De-escalating as feature work to support container networking in vsphere did not make the roadmap. Added vsphere-provider tag.

[Canonical Juju QA Bot (juju-qa-bot)]

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.