Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
sudo systemd-analyze verify irqbalance.service
/usr/lib/systemd/system/irqbalance.service:6: Unknown lvalue 'ConditionCPUs' in section 'Unit'
Version-Release number of selected component (if applicable):
irqbalance-1.9.0-3.el8.x86_64
cat /usr/lib/systemd/system/irqbalance.service
[Unit]
Description=irqbalance daemon
Documentation=man:irqbalance(1)
Documentation=https://github.com/Irqbalance/irqbalance
ConditionVirtualization=!container
ConditionCPUs=>1
[Service]
EnvironmentFile=-/usr/lib/irqbalance/defaults.env
EnvironmentFile=-/etc/sysconfig/irqbalance
ExecStart=/usr/sbin/irqbalance --foreground $IRQBALANCE_ARGS
ReadOnlyPaths=/
ReadWritePaths=/proc/irq
RestrictAddressFamilies=AF_UNIX
RuntimeDirectory=irqbalance/
[Install]
WantedBy=multi-user.target
Additional info:
ConditionCPUs came in with SystemD version 242.
https://github.com/systemd/systemd/blob/main/NEWS#L3941
but in the VM created with rhel-guest-image-8.7-1176.qcow2,
systemctl --version systemd
systemd 239 (239-62.el8)
...
please help to check and fix it.
Confirming that the bug indeed occurs with irqbalance-1.9.0-3, and is fixed in irqbalance-1.9.0-4 ("systemd analyze" does not report the error anymore; from /usr/lib/systemd/system/irqbalance.service I can see that the offending line was removed which probably a good solution for the time being [until new systemd is integrated]).
Thanks to everyone involved!
Removing the line entirely does get rid of the error, but changing the line from
ConditionCPUs=>1
to
ConditionCPUs>=2
is probably the better fix. This allows the service to rebalance IRQs between CPUs where there is more than one CPU present, but doesn't bother running the service when there is only one CPU. Not really a performance enhancement, but it probably stays in-line with the original intent of the configuration.
(In reply to Dennis Stout from comment #13)
> Removing the line entirely does get rid of the error, but changing the line
> from
>
> ConditionCPUs=>1
>
> to
>
> ConditionCPUs>=2
>
> is probably the better fix. This allows the service to rebalance IRQs
> between CPUs where there is more than one CPU present, but doesn't bother
> running the service when there is only one CPU. Not really a performance
> enhancement, but it probably stays in-line with the original intent of the
> configuration.
Hi Dennis,
Thanks for your comments! The systemd version which used currently in rhel8 is systemd-239-74.el8_8.x86_64.rpm, however according to [1], the ConditionCPUs is only available after 242. So I think no matter ConditionCPUs>=?, the variable will not take effect and the same warning "Unknown lvalue 'ConditionCPUs'" will always be outputted.
Thanks,
Tao Liu
[1]: https://github.com/systemd/systemd/blob/main/NEWS#L3941
(In reply to Peter Bieringer from comment #15)
> when will be " irqbalance-1.9.0-4" available? At least on AlmaLinux 8 it's
> still irqbalance-1.9.0-3 as of 2023-04-23
Hi Peter,
Thanks for your comments. irqbalance-1.9.0-4 is in rhel8.8, however I see AlmaLinux 8, it is equivalent to rhel8.7, which the new irqbalance release is not targeted on. The package should be available when rhel8.8 is released.
Thanks,
Tao Liu
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (irqbalance bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2023:3035