VMWare host unavailable on container creation when external network set without DHCP or external IP address

[Merlijn Sebrechts]

# What I did

VMWare vsphere cluster, both internal-network and external-network are set, external-network is set to an interface without an IP. Container networking is set to `provider`.

I add a machine and deploy the Ubuntu charm to a container on that machine.

# Result

When I create a container, the host machine looses network connectivity and the container doesn't come up. If I login to the VM using vmware console, and I run `ifup`, the network is up for a few minutes, and then goes down again.

- juju-debug-log: http://paste.ubuntu.com/26417714/
- brctl: http://paste.ubuntu.com/26417724
- ifconfig: http://paste.ubuntu.com/26417728
- journalctl: http://paste.ubuntu.com/26417729
- route: http://paste.ubuntu.com/26417730

# More info about the setup:

We have two networks: a `primary-network`, running a dhcp server with ddns, and a `external-network` where users need to add an IP address manually. This is because public ip's are very scarce in our organization and we can't just give Juju an entire range.

# Original discussion

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

(This is case #4)

[John A Meinel (jameinel)]

is it possible to also include /etc/network/interfaces
Are you intending to add external addresses to containers that are running (and not giving addresses to the host machine)? Or is nothing going to be publicly exposed?

[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.