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.
Having the CTDB agent use cgexec when available sounds like the least intrusive approach. If the capability could be more broadly useful, it could be added to the resource-agents shell functions.
(In reply to Ken Gaillot from comment #10)
> Having the CTDB agent use cgexec when available sounds like the least
> intrusive approach. If the capability could be more broadly useful, it could
> be added to the resource-agents shell functions.
Maybe there is a trick but simple 'cgexec -g cpu: ...' - the intuitive
way to execute something in the root-cgroup - is failing for me.
If that really doesn't work using cgexec we would be again back to the
situation that we need to setup some cgroup that has a proper realtime-share
assigned. Setting up a realtime-slice with systemd should do the purpose.
So we don't have to make a resource run as systemd-unit but instead we
can simply use 'cgexec -g- cpu:realtime.slice ...'.
Comment 12Oyvind Albrigtsen
2022-08-01 09:28:34 UTC
I'm working on a patch using cgexec.
Comment 13Oyvind Albrigtsen
2022-08-04 08:30:52 UTC
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 (resource-agents 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-2022:7443