SetServiceConstraints API does not remove tags
Bug #1309449 reported by
Francesco Banconi
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Won't Fix
|
Low
|
Unassigned | ||
| juju-gui |
Triaged
|
High
|
Unassigned | ||
Bug Description
The usual behavior of SetServiceConst
The only exception is tags (defined as a *[]string), which is instead preserved.
For consistency, I'd expect tags to be unset as well.
| tags: | added: api |
| Changed in juju-core: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| Changed in juju-gui: | |
| status: | New → Triaged |
| importance: | Undecided → High |
Revision history for this message
| Mark Brown (mstevenbrown) wrote | #1 |
Revision history for this message
| Samantha Jian-Pielak (samantha-jian) wrote | #2 |
| Changed in juju-core: | |
| status: | Triaged → Won't Fix |
To post a comment you must log in.
The apparent net effect of this defect is seen in the following sequence:
$ juju bootstrap --constraints tags=jujusrv #tag was created so juju server goes to correct node
$ juju get-constraints
tags=jujusrv # this tag now constrains whole environment
S juju set-constraints # this usually clears all the constraints, right?
$ juju get-constraints
tags=jujusrv
....and now I cannot deploy ANYTHING.