Can't change max-logs-age or max-logs-size after bootstrap
Bug #1802458 reported by
Paul Gear
This bug report is a duplicate of:
Bug #1682627: changes to log pruning age/size config are not handled.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
High
|
Unassigned | ||
| 2.4 |
Triaged
|
High
|
Unassigned | ||
Bug Description
On high log volume controllers, it's desirable to tune logging; however, this can't be done after bootstrap:
$ juju controller-config
Attribute Value
...
max-logs-age 72h
max-logs-size 4096M
max-txn-log-size 10M
...
$ juju controller-config max-logs-age=48h
ERROR can't change "max-logs-age" after bootstrap
$ juju controller-config max-logs-size=2048M
ERROR can't change "max-logs-size" after bootstrap
Please allow these parameters to be tuned post-bootstrap.
| tags: | added: canonical-is |
| Changed in juju: | |
| importance: | Undecided → High |
| status: | New → Triaged |
| milestone: | none → 2.5-beta1 |
To post a comment you must log in.
