Comment # 20 on bug 1204180 from Ignaz Forster

(In reply to Josef Reidinger from comment #14)
> But question is if it is correct to call it even when kdump is disabled? So
> basically yast knows if kdump is configured and if so, then it ensures that
> kdump rpm package is installed. But we now call that call unconditionally,
> which is maybe wrong?

Indeed, that doesn't seem to be correct, especially when kdump is not even
installed.
If it is installed, but inactive, then transactional-update will not trigger
the script either. I assume that was done for performance reasons, though that
wouldn't always catch the case when the kernel command line is configured and
the admin wants to simply switch the service on and off without calling
`transactional-update kdump` beforehand. However there were no complaints about
that behaviour yet.