--constraints option is ignored on MaaS provider
Bug #1408762 reported by
Gabriel Samfira
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Fix Released
|
High
|
Ian Booth | ||
| 1.21 |
Fix Released
|
High
|
Ian Booth | ||
| 1.22 |
Fix Released
|
High
|
Ian Booth | ||
Bug Description
While testing out juju 1.21 beta5 with a MaaS install, I noticed that the --constraints option is ignored. looking at:
https:/
it appears that the constraints are never sent to acquireNode. The end result is that you get a random node back from MaaS.
Related branches
lp://staging/~wallyworld/gomaasapi/testservice-additions
- Andrew Wilkins (community): Approve
-
Diff: 180 lines (+127/-1)2 files modifiedtestservice.go (+72/-1)
testservice_test.go (+55/-0)
| Changed in juju-core: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| Changed in juju-core: | |
| milestone: | none → 1.21-beta5 |
| Changed in juju-core: | |
| assignee: | nobody → Ian Booth (wallyworld) |
| status: | Triaged → In Progress |
| Changed in juju-core: | |
| milestone: | 1.21-beta5 → 1.22-alpha1 |
| no longer affects: | juju-core/1.21 |
| Changed in juju-core: | |
| milestone: | 1.22-alpha1 → 1.23 |
Revision history for this message
| Curtis Hovey (sinzui) wrote | #1 |
| tags: | added: constraints maas-provider |
Revision history for this message
| John George (jog) wrote | #2 |
| tags: | added: oil |
Revision history for this message
| Larry Michel (lmic) wrote | #3 |
| Changed in juju-core: | |
| status: | In Progress → Fix Committed |
| Changed in juju-core: | |
| status: | Fix Committed → Fix Released |
| Changed in juju-core: | |
| milestone: | 1.23 → 1.23-beta1 |
To post a comment you must log in.
Is this a regression from 1.20.x? If so we need this fix backported to 1.21.