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).
Help
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).
VMWare doesn’t support Spaces and thus multi-nic support. It might be confusing if the template that’s started with includes multiple nics since Juju isn’t prepared to handle it.
@rick_h Its not the same bug, but I’m reading from the conversation that Daniel Bidwell gets the same kind of problem. I’m linking the comment here: Comment #24 : Bug #1800940 : Bugs : juju
The template ( created automatically by the bootstrap ) doesn’t seem to have two nics. I’ll double check tomorrow.
Additional hints to what might be happening here:
After removing the redundant/extra nic and attempting a “juju deploy ubuntu” - the created machine also gets 2 nics with the same MAC as the controller node + all the same cpus, ram, etc. as the controller/bootstrapped node.
I’m also experiencing that I even get 4 nics on the controller node from a bootstrap (!!!) when I’m adding in bootstrap parameters “external-network” + “primary-network”.
Then I performed the exact same bootstrap command as I did with 2.6.8. The resulting controller now gets properly a single nic and subsequent deploys also renders into working machines.
Thanx for the attention. It seems from the discussion in Bug #1844125 that the revert to 2.6.6 still affects Daniel Bidwell, so perhaps this is something else.
The detail I mentioned above, that, when providing “external-network” + “primary-network” the controller gets 4 (four) nics. Maybe that would help you track down where this happens.
