juju get incorrectly reports boolean default values
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
High
|
Menno Finlay-Smits | ||
1.25 |
Fix Released
|
High
|
Menno Finlay-Smits |
Bug Description
Juju get incorrectly reports (at least some) boolean default values incorrectly, but it does set them to the correct value. This makes it look like the value has been changed from the default when it hasn't.
For example, with ntp:
$ juju get ntp
charm: ntp
service: ntp
settings:
auto_peers:
default: true
description: Will ntp auto peer between the environment
type: boolean
value: false
Checking on disk in the charm's config.yaml:
auto_peers:
default: false
type: boolean
description: Will ntp auto peer between the environment
The same applies to the other boolean values I checked. The end effect is that the right setting is being deployed, but it is misleading.
$ juju --version
1.24.5-trusty-amd64
Please let me know if you need any more information.
Changed in juju-core: | |
importance: | Undecided → High |
milestone: | none → 1.25-beta2 |
Changed in juju-core: | |
status: | New → Triaged |
Changed in juju-core: | |
assignee: | nobody → Menno Smits (menno.smits) |
Changed in juju-core: | |
status: | Triaged → In Progress |
Changed in juju-core: | |
milestone: | 1.25-beta2 → 1.26-alpha1 |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
tags: | added: sts |
no longer affects: | juju-core/2.0 |
Finding so far:
The default shown for all config options by "juju get" is "true" even for non-boolean options.
The problem is with the ServiceGet API call. The client code is simply dumping out what the API call returns.