https://bugzilla.suse.com/show_bug.cgi?id=1204180 https://bugzilla.suse.com/show_bug.cgi?id=1204180#c13 Ignaz Forster <iforster@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(iforster@suse.com | |) | --- Comment #13 from Ignaz Forster <iforster@suse.com> --- (In reply to Josef Reidinger from comment #12)

2. In previous ages for CAASP product we add that specific call that is called always for kdump, even when kdump is not enabled ( see comment#8 for code ). I am not sure if it is correct to call it always.

I think this code is still needed for openSUSE MicroOS / SLE Micro / ALP, otherwise kdump wouldn't be configured on first boot I guess?

3. I am not sure if `transactional-update kdump` handle disabled kdump. We need to have it when user configure kdump and then change mind. Is it correct to call also `transactional-update kdump` in that case?

Yes, it checks whether the kdump.service is activated and only runs if that is the case. However that check is performed in transactional-update itself, not in /usr/sbin/tu-rebuild-kdump-initrd, the helper script which is called from YaST directly during installation (where Package.IsTransactionalSystem doesn't seem to be true from how I understand the code). -- You are receiving this mail because: You are on the CC list for the bug.