Bug 1215725

Summary:	Hint user when calling incorrect kdump command
Product:	[openSUSE] PUBLIC SUSE Linux Enterprise Micro 5.5	Reporter:	Jiri Srain <jsrain>
Component:	Transactional Update	Assignee:	Ignaz Forster <iforster>
Status:	RESOLVED FIXED	QA Contact:	Jiri Srain <jsrain>
Severity:	Enhancement
Priority:	P3 - Medium	CC:	marius.kittler, prokop.vlasin
Version:	unspecified
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Jiri Srain 2023-09-26 13:45:11 UTC

When calling 'transactional-update kdump' without previously enabling kdump, it runs quite fast, but does not enable kdump, which may be what user (incorrectly) expects.

It would be good that if 'transactional-update kdump', when called before enabling kdump via 'transactional-update setup-kdump', issued at least a warning to the user pointing him he used wrong command. I think that detection based on crash kernel boot parameter could be sufficient, unless you have better idea.

Accidentally mixing the commands happened to me just today.

Comment 1 Marius Kittler 2023-09-26 15:06:10 UTC

This would be useful indeed, see bsc#1215717.

Comment 2 Ignaz Forster 2023-10-06 15:51:45 UTC

If installed, the kdump initrd rebuild has to be triggered from quite a lot of places in the transactional-update code, but doesn't do anything if the kdump service is not installed.

The logic in the central call has been changed now: If the `kdump` command was specified explicitly, but kdump.service is not enabled in the new snapshot, the user will receive an info message now. This includes cases where kdump is installed, but not active (which would also be "fixed" by calling `setup-kdump`).

Changed in https://github.com/openSUSE/transactional-update/commit/4bf9f329719d150fbe95faa7cbfb0a5eee0d996e

Comment 3 Ignaz Forster 2023-10-06 15:54:45 UTC

I should add: This change will only be available in SLE Micro 6.0 because the codebase of SLE Micro 5.x is a bit dated now...

Comment 4 OBSbugzilla Bot 2023-11-21 15:35:01 UTC

This is an autogenerated message for OBS integration:
This bug (1215725) was mentioned in
https://build.opensuse.org/request/show/1127927 Factory / transactional-update