I’m facing problems bootstrapping a vsphere controller at the moment.
(See: JAAS | Juju )
The controller machine (and subsequent deploys) creates machines with 2 nic:s with the same MAC addresses and hence the same IP-address:es. This obviously causes networking issues and I’m not sure what part juju has in this atm.
Subsequent “juju deploy foobar” equally creates machines with this very same problem (even reusing the MAC-address from the juju controller host).
I’m trying to figure out if the problem is in vsphere or in juju. Since this worked fine on a previous controller (unfortunately torn down so I don’t know the version).
I bootstrap with the following:
juju bootstrap vmware01 iuba-vmware --config config.yaml --bootstrap-constraints=“mem=32G cores=8” --model-default model-default.yaml
The content of config.yaml:
The content of the model-default.yaml:
The resulting controller machine ends up with 2 nic:s as the picture below
The MAC-addresses are the same on those NIC:s and hence also given the same IP-addresses.
This never happened before. The version of juju is: 2.6.8-bionic-amd64
juju 2.6.8 8873 stable canonical✓ classic
Anyone that has a clue on whats going wrong here?
Things I’ve tried with no avail:
- Messing around with external-network and primary-network with no avail.
- Messing around with templates.