Intermitent problem with 'zone' placement directive when bootstraping remote LXD cluster cloud
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
High
|
Simon Richardson | ||
Bug Description
I initially tried, and failed, to do this on a remote LXD cluster:
$ juju bootstrap lxd-cluster --to zone=node3
Creating Juju controller "lxd-cluster-
Looking for packaged Juju agent version 2.5-beta1 for amd64
No packaged binary found, preparing local Juju agent binar
To configure your system to better support LXD containers, please see: https:/
Launching controller instance(s) on lxd-cluster/
ERROR failed to bootstrap model: cannot start bootstrap instance in availability zone "node3": Failed container creation: Image 'c395a710527871
I then tried this vanilla invocation, which worked:
$ juju bootstrap lxd-cluster
Killing the controller and retrying worked:
$ juju kill-controller -y lxd-cluster-default
$ juju bootstrap lxd-cluster --to zone=node3
| Changed in juju: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| assignee: | nobody → Joseph Phillips (manadart) |
| milestone: | none → 2.5-beta1 |
| Changed in juju: | |
| assignee: | Joseph Phillips (manadart) → Simon Richardson (simonrichardson) |
| Simon Richardson (simonrichardson) wrote | #1 |
| Changed in juju: | |
| status: | Triaged → In Progress |
| Changed in juju: | |
| status: | In Progress → Fix Committed |
| Changed in juju: | |
| status: | Fix Committed → Fix Released |
You can follow the submitted PR here https:/