Juju --constraints "zones=NAME WITH SPACES" fails because of space chars
Bug #1847259 reported by
Pedro Guimarães
This bug affects 5 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Achilleas Anagnostopoulos | ||
2.8 |
Fix Released
|
High
|
Achilleas Anagnostopoulos |
Bug Description
Juju: 2.6.9
Juju fails when defining constraints with space-separated values since it depends on spaces for its list. So, a constraint list like:
--constraints "mem=A cores=B zones=NAME WITH SPACES"
Will obviously fail. But there is no alternative to add spaces to that name, like:
--constraints "mem=A cores=B zones=NAME\ WITH\ SPACES"
or
--constraints "mem=A cores=B zones='NAME WITH SPACES'"
summary: |
- Juju --constraints "zones=NAME WITH SPACES" fails because of spaces + Juju --constraints "zones=NAME WITH SPACES" fails because of space + chars |
Changed in juju: | |
assignee: | Nam Nguyen (nammn) → nobody |
Changed in juju: | |
milestone: | 2.7-beta1 → 2.7-rc1 |
Changed in juju: | |
milestone: | 2.7-rc1 → none |
Changed in juju: | |
milestone: | none → 2.7.7 |
status: | Triaged → Fix Committed |
assignee: | nobody → Achilleas Anagnostopoulos (achilleasa) |
Changed in juju: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Current work-around available is to run "add-machine" to force VMs to be created to the right place. It still demands a step before "juju deploy" and will always demand 2 steps at deployment:
1) juju add-machine
2) juju add-unit --to=NEW_MACHINE