juju fails when requesting an IP for a container when retrying after lxd forkstart
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
John A Meinel | ||
2.1 |
Fix Released
|
High
|
John A Meinel |
Bug Description
juju is trying to start a container, hits a lxd forkstart error, then retries, but gets an error trying to reserve an IP for the container with MAAS, because it already reserved an IP before hitting the lxd forkstart error. This causes the container to end up without a MAAS allocated IP, which in 2.1.0 causes it to show up with a private LXD IP.
http://
jam says this would result in an error/failed provisioning in 2.1.1, but that it still needs to be fixed to reuse the original IP address juju got from maas.
Here is the broader log: http://
Here is juju status: http://
This is with 2.1.0.1 controller.
description: | updated |
description: | updated |
summary: |
- juju requesting an IP for a container when retrying after lxd forkstart + juju fails when requesting an IP for a container when retrying after lxd + forkstart |
Changed in juju: | |
milestone: | 2.2-beta1 → 2.2-alpha1 |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
I don't know that we'll actually try to fix this for 2.1, but it does seem like a small valid fix. We may punt and just roll it all into 2.2, but I'll fix it targeting 2.1 and we can decide whether its worth a release there.