Bug 2059242

Summary:	[RFE] coredumpctl should trigger sosreport generation
Product:	Red Hat Enterprise Linux 9	Reporter:	Piyush Bhoot <pbhoot>
Component:	sos	Assignee:	Pavel Moravec <pmoravec>
Status:	NEW ---	QA Contact:	Supportability QE <supportability-qe>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	9.0	CC:	agk, cww, dtardon, fkrska, jcastillo, msekleta, plambri, sbradley, systemd-maint-list, theute
Target Milestone:	rc	Keywords:	FutureFeature, Triaged
Target Release:	---	Flags:	pmoravec: needinfo? (cww)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Story
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Comment 5 Lukáš Nykrýn 2023-08-03 14:00:09 UTC

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

Comment 6 Pavel Moravec 2023-08-06 13:23:01 UTC

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?

Comment 7 Lukáš Nykrýn 2023-08-08 10:40:21 UTC

(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.