Need method of specifying cache: no-negative in /etc/systemd/resolved.conf
Bug #1841809 reported by
Paul Goins
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
charm-sysconfig |
Fix Released
|
High
|
Unassigned |
Bug Description
To avoid recurrence of bug #1668771, it would be good to have a charmed way of setting the cache: no-negative option in /etc/systemd/
It feels like we should have some sort of systemd configuration charm. It seems like we may have something close to that in the sysconfig charm, however that charm seems presently heavily focused on CPU governor settings. Maybe this issue will expand that charm's scope? Or do we need another charm for this?
Related branches
~vultaire/charm-sysconfig:lp1841809
- Jeremy Lounder (community): Approve
- Alvaro Uria (community): Approve
-
Diff: 473 lines (+171/-83)6 files modifiedsrc/config.yaml (+6/-0)
src/lib/lib_sysconfig.py (+48/-18)
src/reactive/sysconfig.py (+9/-1)
src/templates/etc.systemd.resolved.conf.j2 (+27/-0)
src/tests/functional/test_deploy.py (+40/-30)
src/tests/unit/test_lib.py (+41/-34)
Changed in bootstack-ops: | |
assignee: | nobody → Paul Goins (vultaire) |
Changed in charm-sysconfig: | |
assignee: | nobody → Paul Goins (vultaire) |
no longer affects: | bootstack-ops |
Changed in charm-sysconfig: | |
status: | In Progress → Fix Committed |
Changed in charm-sysconfig: | |
milestone: | none → 20.02 |
Changed in charm-sysconfig: | |
importance: | Undecided → High |
To post a comment you must log in.
Moved from bootstack-ops to charm-sysconfig.