--constraints option is ignored on MaaS provider

Bug #1408762 reported by Gabriel Samfira
20
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://github.com/juju/juju/blob/master/provider/maas/environ.go#L802

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

Changed in juju-core:
status: New → Triaged
importance: Undecided → High
Changed in juju-core:
milestone: none → 1.21-beta5
Ian Booth (wallyworld)
Changed in juju-core:
assignee: nobody → Ian Booth (wallyworld)
status: Triaged → In Progress
Ian Booth (wallyworld)
Changed in juju-core:
milestone: 1.21-beta5 → 1.22-alpha1
no longer affects: juju-core/1.21
Ian Booth (wallyworld)
Changed in juju-core:
milestone: 1.22-alpha1 → 1.23
Revision history for this message
Curtis Hovey (sinzui) wrote :

Is this a regression from 1.20.x? If so we need this fix backported to 1.21.

tags: added: constraints maas-provider
Revision history for this message
John George (jog) wrote :

It is a regression from 1.20.14, see comment #4 in bug 1411042.

tags: added: oil
Revision history for this message
Larry Michel (lmic) wrote :

beta5 seems to be working for us. It's picking servers with the right tag for the builds we've had with this fix.

Ian Booth (wallyworld)
Changed in juju-core:
status: In Progress → Fix Committed
Curtis Hovey (sinzui)
Changed in juju-core:
status: Fix Committed → Fix Released
Curtis Hovey (sinzui)
Changed in juju-core:
milestone: 1.23 → 1.23-beta1
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.