Problem parsing complex values in grub-config-flags

Bug #2020477 reported by Vidar Tyldum
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
charm-sysconfig
Fix Released
Undecided
Unassigned

Bug Description

So I'm trying to properly isolate a real-time workload on OpenStack, and need to set "nohz_full" and "rcu_nocbs" for the same cores as was set in "isolcpus". There are no dedicated settings in the charm so I rely on setting grub-config-flags.

$ juju config sysconfig grub-config-flags='GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT nvme_core.multipath=0 nohz_full=22-39,62-79 rcu_nocbs=22-39,62-79"'

Renders (notice, a comma becomes a newline):

GRUB_CMDLINE_LINUX_DEFAULT=$GRUB_CMDLINE_LINUX_DEFAULT nvme_core.multipath=0 nohz_full=22-39
62-79 rcu_nocbs=22-39,62-79

while I would expect is to be:
GRUB_CMDLINE_LINUX_DEFAULT=$GRUB_CMDLINE_LINUX_DEFAULT nvme_core.multipath=0 nohz_full=22-39,62-79 rcu_nocbs=22-39,62-79

Vidar Tyldum (tyldum)
description: updated
description: updated
description: updated
description: updated
Revision history for this message
Eric Chen (eric-chen) wrote :

This issue should be fixed in
https://code.launchpad.net/~dashmage/charm-sysconfig/+git/charm-sysconfig/+merge/441304

Please test the version in edge channel. thanks!

Changed in charm-sysconfig:
status: New → Fix Committed
Ashley James (dashmage)
Changed in charm-sysconfig:
milestone: none → 23.07
Ashley James (dashmage)
Changed in charm-sysconfig:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.