Red Hat Bugzilla – Bug 798717
The ksmtuned.service has no "retune" operation
Last modified: 2014-01-12 18:54:03 EST
VDSM uses the retune operation of the ksmtuned service, while this operation does not exist in Fedora 16 systemd's ksmtuned.service
Thread-16093::DEBUG::2012-02-29 16:55:23,705::utils::601::Storage.Misc.excCmd::(execCmd) '/usr/bin/sudo -n /sbin/service ksmtuned retune' (cwd None)
Thread-16093::DEBUG::2012-02-29 16:55:23,746::utils::601::Storage.Misc.excCmd::(execCmd) FAILED: <err> = 'Unknown operation retune\n'; <rc> = 1
I would say that this is a ksmtuned bug, not Vdsm's. Also, this may become redundant with MOM looming in http://gerrit.ovirt.org/2367
Until it becomes redundant, note that the side effect of the above problem is more external commands that don't care that the "retune" operation failed:
"pgrep -xf ksmd"
"kill -9 process_id" - fails
Please disregard my last comment, it's not related to this bug.
(In reply to comment #1)
> I would say that this is a ksmtuned bug, not Vdsm's. Also, this may become
> redundant with MOM looming in http://gerrit.ovirt.org/2367
Hmm, there is no 'retune' command for systemd controlled daemons. I see in /usr/lib/systemd/system/ksmtuned.service on my f17 machine that 'retune' has now been remapped to 'reload'. I believe the best solution is for VDSM to support both - switching commands depending on which interface (service or systemctl) is used for the system. Using 'service' to manage systemd scripts as is shown in comment 0 should be avoided as well.
Starting oVirt 3.3 vdsm will use mom and ksm without ksmtuned. See bug 987926.
Therefore this issue is no longer relevant, and closing as such.
OK. Any info requested from my side?
(In reply to Rami Vaknin from comment #6)
> OK. Any info requested from my side?
No info needed. Just wanted you to notice.