cpu-affinity-range not applied when changing charm config
Bug #1913325 reported by
Gábor Mészáros
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
charm-sysconfig |
Fix Released
|
High
|
Unassigned |
Bug Description
there's a missing flag to be checked when config-changed.
Related branches
~peppepetra/charm-sysconfig:lp1913325
- 🤖 prod-jenkaas-bootstack (community): Approve (continuous-integration)
- BootStack Reviewers: Pending requested
- BootStack Reviewers: Pending requested
-
Diff: 31 lines (+11/-2)1 file modifiedsrc/reactive/sysconfig.py (+11/-2)
~gabor.meszaros/charm-sysconfig:master
Rejected
for merging
into
charm-sysconfig:master
- Giuseppe Petralia: Needs Fixing
- 🤖 prod-jenkaas-bootstack (community): Needs Fixing (continuous-integration)
- Xav Paice (community): Needs Information
- Drew Freiberger (community): Needs Information
-
Diff: 13 lines (+2/-1)1 file modifiedsrc/reactive/sysconfig.py (+2/-1)
tags: | added: bseng-485 |
Changed in charm-sysconfig: | |
status: | Confirmed → Fix Released |
To post a comment you must log in.
There is a functional test that ensures this setting is changed.
https:/ /git.launchpad. net/~gabor. meszaros/ charm-sysconfig /tree/src/ tests/functiona l/test_ deploy. py#n214
Can you please help by explaining the exact scenario and versions of the charm you are running and what failed?
Is the issue that the file isn't updated, or is it that systemd needs to be daemon_reloaded, or did you have a service that needed restarted after the change was applied?