juju deploy without constraints can render an unusable unit
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Joseph Phillips |
Bug Description
When deploying a new application without the correct constraints juju will end up deploying an application with bindings to a machine that won't have the necessary NICs. This was observed using juju 2.14 and openstack provider.
Test Case:
juju add-model test
juju add-space main 10.0.0.0/24
juju add-space external 10.10.0.0/24
# nagios-a will be allocated to a machine with a single NIC
juju deploy --bind 'main public=external' cs:nagios nagios-a
# nagios-b will be allocated to a machine with 2 NICs as requested by the constraint
juju deploy --bind 'main public=external' --constraints "spaces=
Here it's the output of my terminal when testing this use case:
https:/
The expected behavior is that juju errors out when it finds that bindings to spaces that the machine doesn't have a ethernet device on OR when --constraints is not passed use the spaces binded for the application.
summary: |
- juju deploy without constraints can render an usable unit + juju deploy without constraints can render an unusable unit |
Changed in juju: | |
status: | New → Triaged |
Changed in juju: | |
status: | Triaged → In Progress |
assignee: | nobody → Joseph Phillips (manadart) |
milestone: | 2.9-next → 2.9.17 |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
Juju deployments are optimistic by default. There are no plans to change that at this moment. I add this to the wishlist.