provisioning fails during deploy when space specified as a constraint
Bug #1947025 reported by
Heather Lanigan
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
High
|
Unassigned | ||
Bug Description
juju 2.9.16
Per our docs:
* https:/
* juju deploy --help
`juju deploy mysql -n 2 --constraints spaces=database` should work.
However provisioning fails with "unable to satisfy supplied space requirements; spaces: [heather], bindings: [alpha]"
`juju deploy mysql --bind database` does work, as does `juju add-machine --constraints spaces=heather`
It's a high if it should work, otherwise lower priority and fix the docs.
| tags: | added: ju-15 |
| tags: | removed: ju-15 |
| tags: | added: usability |
Revision history for this message
| Peter Matulis (petermatulis) wrote | #1 |
To post a comment you must log in.
@Heather
Depending on your provider setup (MAAS cluster) in terms of available spaces you may need to also specify a binding. On Juju 2.9.38, this worked for me:
juju deploy --constraints spaces=oam-space --bind public-space ubuntu
juju show-application ubuntu
ubuntu:
charm: ubuntu
series: jammy
channel: stable
constraints:
arch: amd64
spaces:
- oam-space
principal: true
exposed: false
remote: false
life: alive
endpoint-
"": public-space