remove outdated model-config key
Bug #1898118 reported by
Andrea Ieri
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
High
|
Heather Lanigan | ||
Bug Description
I have a cloud that was upgraded from juju 1.x. The controller logs are constantly (4 times/second) spammed with:
2020-10-01 20:03:51 WARNING juju.environs.
2020-10-01 20:03:51 WARNING juju.environs.
2020-10-01 20:03:51 WARNING juju.environs.
2020-10-01 20:03:51 WARNING juju.environs.
I believe those keys used to be valid model-config attributes under juju 1, but not anymore. How can I remove them? I am only able to modify their values, not delete the attribute altogether.
Revision history for this message
| Andrea Ieri (aieri) wrote | #1 |
| Changed in juju: | |
| milestone: | none → 2.9-rc1 |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| tags: | added: bitesize |
| Changed in juju: | |
| importance: | Medium → High |
| Changed in juju: | |
| assignee: | nobody → Heather Lanigan (hmlanigan) |
Revision history for this message
| Heather Lanigan (hmlanigan) wrote | #2 |
| Changed in juju: | |
| status: | Triaged → In Progress |
| Changed in juju: | |
| status: | In Progress → Fix Committed |
| Changed in juju: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Ok scratch that, resetting the keys removed them from model-config.
I suggest explaining this behavior in the `juju model-config --help` output, though.