juju deployed LXD inherit constraints from the host causing lxd deploys to fail
Bug #1685782 reported by
james beedy
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Witold Krecicki |
Bug Description
As of 2.1.2, my lxd instances fail to deploy when the 'spaces' constraint is supplied for the host using the AWS provider.
This is critical because it puts a dead stop to anything being deployed to lxd on a host that uses the spaces constraint after 2.1.2.
To reproduce (must be Juju 2.1.2):
$ juju deploy ubuntu --constraints "spaces=myspace" # gets id 0
$ juju deploy ubuntu ubuntu-lxd --to lxd:0
The ubuntu-lxd deploy will absolutely fail with the lxd showing a "down" status, and message "unable to find host bridge for space(s) "myspace" for container".
Juju 2.1.2 (Fail) - http://
Juju 2.0.3 (Working) - http://
description: | updated |
Changed in juju: | |
status: | New → Incomplete |
status: | Incomplete → New |
description: | updated |
tags: | added: constraints network spaces |
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in juju: | |
assignee: | nobody → Witold Krecicki (wpk) |
importance: | Medium → High |
Changed in juju: | |
status: | Triaged → In Progress |
milestone: | none → 2.2-rc1 |
Changed in juju: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
This is blocking my use case 100%. I can't spin up my own pre 2.1 controller and migrate my JAAS models over to my own controller because no migrations < 2.1.x, and can't deploy anything more on the JAAS controller due to this. My lxd deploys are dead in the water until this gets patched.