Merge lp:~dpb/juju-deployer/lxc-placement-fix into lp:juju-deployer
Proposed by
David Britton
Status: | Merged | ||||
---|---|---|---|---|---|
Merged at revision: | 120 | ||||
Proposed branch: | lp:~dpb/juju-deployer/lxc-placement-fix | ||||
Merge into: | lp:juju-deployer | ||||
Prerequisite: | lp:~dpb/juju-deployer/api-endpoints | ||||
Diff against target: |
55 lines (+16/-4) 3 files modified
deployer/service.py (+4/-3) deployer/tests/test_data/stack-placement.yaml (+4/-0) deployer/tests/test_deployment.py (+8/-1) |
||||
To merge this branch: | bzr merge lp:~dpb/juju-deployer/lxc-placement-fix | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Kapil Thangavelu | Approve | ||
Review via email: mp+230924@code.launchpad.net |
Description of the change
I'm pretty sure a simple variable error/typo caused this bug. The fall-through behavior of the routine was correct, but an early exit was checking the wrong variable making the default placement algorithm take over too soon.
I changed the variable being tested and cleaned up the warning message a bit. I also added a unit test for this case (which runs and fails on the old code)
To post a comment you must log in.
Thanks, merged