juju config returns <nil> for empty config (2.4.2)
Bug #1789415 reported by
Edward Hope-Morley
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Anastasia | ||
2.3 |
Fix Released
|
High
|
Anastasia | ||
2.4 |
Fix Released
|
Critical
|
Anastasia |
Bug Description
Up until 2.4.1 juju would return an empty string "" for configs that were unset but with 2.4.2 I now get "<nil>"
ubuntu@
2.4.1-xenial-amd64
ubuntu@
ubuntu@
ubuntu@
2.4.2-xenial-amd64
ubuntu@
<nil>
I assume this is unintentional
description: | updated |
description: | updated |
tags: | added: sts ui |
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → Critical |
milestone: | none → 2.4.3 |
tags: | added: uosci |
Changed in juju: | |
assignee: | nobody → Ian Booth (wallyworld) |
Changed in juju: | |
assignee: | Ian Booth (wallyworld) → Anastasia (anastasia-macmood) |
Changed in juju: | |
status: | Triaged → In Progress |
Changed in juju: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Yes, it is unintentional. We'll get right on it.