Description of problem: The ceph-rbd-mirror@.service file uses a "TasksMax" setting, which causes an error to be printed, eg "systemctl status ceph-rbd-mirror" systemd introduced this TasksMax setting in version 226, while RHEL 7 still has systemd 219. Version-Release number of selected component (if applicable): ceph-10.2.0-1.el7cp How reproducible: always Steps to Reproduce: 1. yum install rbd-mirror 2. systemctl start ceph-rbd-mirror 3. systemctl status -l ceph-rbd-mirror Actual results: May 12 14:44:42 magna004 systemd[1]: [/usr/lib/systemd/system/ceph-rbd-mirror@.service:20] Unknown lvalue 'TasksMax' in section 'Service' Expected results: service starts as expected, without warning about TasksMax.
Boris, would you please fix this issue with the systemd unit file for ceph-rbd-mirror?
(Note to QE: this only applies to RHEL, since Ubuntu Xenial ships systemd 229)
@Ken: SystemD ignores the lines that it does not understand and prints the warning (not error) to the journal. Otherwise, it will continue as if the line was not there. I don't think there is anything we need to do, here (well, if we are ok that TasksMax won't apply). i.e.: The warning does not have any additional influence on the functionality of the service. It is just that the maximum number of tasks won't be enforced afterwards.
We could make the packaging strip out this line during the RHEL 7 build.
That would work. The downside is that we would need to un-apply the change once (or if) RHEL 7 adopts that option for it to take action (*). (*) In terms of enterprise sw, this might be considered an upside as it minimizes the amount of available (untested) variants. :-)
Given that the option preserves the current behaviour (if it is applicable) and all it does is that prints a warning (well, an info message) to the journal on a system that does not support it, I think that the safest choice for us, here, would be to just keep it the way it is, now.
NOTE: We might want to document this somewhere (KB?) to minimize to volume of support calls that it could potentially generate.
From the systemd bug 1337244, we're clear to just strip out the TasksMax setting on RHEL 7.
According to bz 1337244, systemd in RHEL 7.4 might make this problem go away.
To summarize this issue: it is entirely cosmetic (TasksMax has no effect in RHEL 7.3.) There is a chance that RHEL 7.4 will make the warning go away.