Closes: coreos#2542

Today anyone wanting to switch to a different kernel variant
such as `kernel-rt` must manually pass all the *current* kernel
packages to `--uninstall` (separately).  It's not just very unergonomic,
it also makes the calling code *operating system dependent* because
as just happened when C9S added a `kernel-modules-core` package,
that suddenly also needs to be specified.

xref https://issues.redhat.com/browse/OCPBUGS-8113

Closes: coreos#2542

Today anyone wanting to switch to a different kernel variant
such as `kernel-rt` must manually pass all the *current* kernel
packages to `--uninstall` (separately).  It's not just very unergonomic,
it also makes the calling code *operating system dependent* because
as just happened when C9S added a `kernel-modules-core` package,
that suddenly also needs to be specified.

xref https://issues.redhat.com/browse/OCPBUGS-8113

Closes: coreos#2542

Today anyone wanting to switch to a different kernel variant
such as `kernel-rt` must manually pass all the *current* kernel
packages to `--uninstall` (separately).  It's not just very unergonomic,
it also makes the calling code *operating system dependent* because
as just happened when C9S added a `kernel-modules-core` package,
that suddenly also needs to be specified.

xref https://issues.redhat.com/browse/OCPBUGS-8113

Closes: coreos#2542

Today anyone wanting to switch to a different kernel variant
such as `kernel-rt` must manually pass all the *current* kernel
packages to `--uninstall` (separately).  It's not just very unergonomic,
it also makes the calling code *operating system dependent* because
as just happened when C9S added a `kernel-modules-core` package,
that suddenly also needs to be specified.

xref https://issues.redhat.com/browse/OCPBUGS-8113

Unfortunately rpm-ostree requires this right now; we have an issue
and code to provide a better API in coreos/rpm-ostree#2542
But using that will require shipping the updated rpm-ostree in RHEL 8.6.z
or at least OCP 4.12.z, which is problematic.

Because we know the new MCD will always be upgrading to RHEL9,
for now let's update this hardcoded list.  In the future we can
detect when the running host has `--remove-installed-kernel` and
use it instead.

Unfortunately rpm-ostree requires this right now; we have an issue
and code to provide a better API in coreos/rpm-ostree#2542
But using that will require shipping the updated rpm-ostree in RHEL 8.6.z
or at least OCP 4.12.z, which is problematic.

Because we know the new MCD will always be upgrading to RHEL9,
for now let's update this hardcoded list.  In the future we can
detect when the running host has `--remove-installed-kernel` and
use it instead.

Unfortunately rpm-ostree requires this right now; we have an issue
and code to provide a better API in coreos/rpm-ostree#2542
But using that will require shipping the updated rpm-ostree in RHEL 8.6.z
or at least OCP 4.12.z, which is problematic.

Because we know the new MCD will always be upgrading to RHEL9,
for now let's update this hardcoded list.  In the future we can
detect when the running host has `--remove-installed-kernel` and
use it instead.

Unfortunately rpm-ostree requires this right now; we have an issue
and code to provide a better API in coreos/rpm-ostree#2542
But using that will require shipping the updated rpm-ostree in RHEL 8.6.z
or at least OCP 4.12.z, which is problematic.

Because we know the new MCD will always be upgrading to RHEL9,
for now let's update this hardcoded list.  In the future we can
detect when the running host has `--remove-installed-kernel` and
use it instead.

Closes: coreos#2542

Today anyone wanting to switch to a different kernel variant
such as `kernel-rt` must manually pass all the *current* kernel
packages to `--uninstall` (separately).  It's not just very unergonomic,
it also makes the calling code *operating system dependent* because
as just happened when C9S added a `kernel-modules-core` package,
that suddenly also needs to be specified.

xref https://issues.redhat.com/browse/OCPBUGS-8113