juju set-env fails for boolean attributes
Bug #1254938 reported by
Ian Booth
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| juju-core | Status tracked in Trunk | |||||
| 1.16 |
Fix Released
|
Critical
|
Ian Booth | |||
| Trunk |
Fix Released
|
High
|
Ian Booth | |||
| juju-core (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | |||
| Saucy |
Won't Fix
|
Undecided
|
Unassigned | |||
Bug Description
[Impact]
Users can't change the value of boolean environent attributes
[Test Case]
juju bootstrap
juju set-env use-floating-
[Regression Potential]
Minimal - impact only in direct code path.
[Original bug report]
If I bootstrap a juju environment, and try to change the value of a boolean environment attribute, I get an error.
$juju set-env some-bool-attr=true
ERROR some-bool-attr: expected bool, got string("true")
Raising as critical because this bug hinders the solution for bug 1254729 which requires the environment to be able to be updated to toggle a boolean flag
Related branches
lp:~wallyworld/juju-core/set-env-boolean
- Juju Engineering: Pending requested
-
Diff: 184 lines (+75/-23)4 files modifiedcmd/juju/environment_test.go (+13/-1)
environs/config/config_test.go (+2/-2)
schema/schema.go (+34/-10)
schema/schema_test.go (+26/-10)
lp:~wallyworld/juju-core/env-set-boolean-1.16
- Ian Booth: Approve
-
Diff: 183 lines (+74/-23)4 files modifiedcmd/juju/environment_test.go (+12/-1)
environs/config/config_test.go (+2/-2)
schema/schema.go (+34/-10)
schema/schema_test.go (+26/-10)
| Changed in juju-core: | |
| assignee: | nobody → Ian Booth (wallyworld) |
| status: | Triaged → In Progress |
| Changed in juju-core: | |
| status: | Fix Committed → Fix Released |
| tags: | added: docs |
| tags: | removed: docs |
| Changed in juju-core (Ubuntu): | |
| status: | New → Fix Released |
| description: | updated |
Revision history for this message
| Rolf Leggewie (r0lf) wrote | #1 |
| Changed in juju-core (Ubuntu Saucy): | |
| status: | New → Won't Fix |
To post a comment you must log in.
saucy has seen the end of its life and is no longer receiving any updates. Marking the saucy task for this ticket as "Won't Fix".