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.
I don't think we wat to add such rhel specific feature to systemd.
But this can be very easily done in sos package.
Just provide a service unit that will create the report and have it activated by path unit.
Here is some example of such unit files
[root@vm-10-0-184-184 system]# cat /usr/lib/systemd/system/sos-on-core.path
[Path]
PathChanged=/var/lib/systemd/coredump
[Install]
WantedBy=paths.target
[root@vm-10-0-184-184 system]# cat /usr/lib/systemd/system/sos-on-core.service
[Service]
Type=oneshot
ExecStart=echo Hello
sos is a debugging tool, not monitoring.
Also, the configuration/feature "let sos report is generated on a coredump" should be configurable; default installation of sos package should not set that up. So, *how* sos can contain or deliver this feature?
I am rather for writing a KCS solution to let customers to create that service unit (and optionally configure the sos report args per their needs).
cww, what do you think?
(In reply to Pavel Moravec from comment #6)
> sos is a debugging tool, not monitoring.
>
> Also, the configuration/feature "let sos report is generated on a coredump"
> should be configurable; default installation of sos package should not set
> that up. So, *how* sos can contain or deliver this feature?
Those unit files can be disabled by default. And in KB we could just write
"call systemctl enable sos-on-core.path "
>
> I am rather for writing a KCS solution to let customers to create that
> service unit (and optionally configure the sos report args per their needs).
>
Yep, that would work as well, those two unit files are super simple.
Comment 8RHEL Program Management
2023-08-28 07:28:22 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.