Add-unit with a KVM fails to warn about spaces
Bug #1804308 reported by
Michael Skalka
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
When adding a kvm container unit of an existing service using `juju add-unit <service> --to kvm:<machine>` if there are multiple spaces available on that machine Juju will fail to warn the user and deploy the node resulting in the following error in the machine section of the juju status:
failed to start machine 0/kvm/0 (unable to setup network: no obvious space for container "0/kvm/0", host machine has spaces: "one", "undefined"), retrying in 10s (8 more attempts)
Changed in juju: | |
milestone: | 2.5.1 → 2.5.2 |
Changed in juju: | |
milestone: | 2.5.2 → 2.5.3 |
Changed in juju: | |
milestone: | 2.5.3 → 2.5.4 |
Changed in juju: | |
milestone: | 2.5.4 → 2.5.5 |
Changed in juju: | |
milestone: | 2.5.6 → 2.5.8 |
Changed in juju: | |
milestone: | 2.5.8 → 2.5.9 |
To post a comment you must log in.
We should make this like the lxd code where if you've not used any spaces in the model yet we don't require you to bind endpoints. If you do have spaces work in the model then we require explicit placements to avoid guessing.