container provisioning failure causes "Node with this Hostname already exists" failure
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
High
|
John A Meinel | ||
Bug Description
I just worked with Jason Hobbs to investigate a failure of this sort.
The symptom was actually bug #1656326 but this is splitting out the concrete failure that was being masked by that bug.
Specifically, Juju is trying to create a container, it talks to MAAS to register a new 'device' with its MAC address. It then goes to launch the container, and would get a failure from 'lxd forkstart' in this particular case.
It then set the container to failed provisioning, but was prepared to retry provisioning the container.
Juju then tried again to provision the container, and it would go to register the 'new' device with MAAS, but MAAS would return "Node with this Hostname already exists". (bug #1656326 meant that this error would get suppressed and then juju would fall back to using lxdbr0 and you would just end up with a container that would be on the wrong bridge.)
