[elrepo] RHEL8 kernels immediately overwritten

[Joseph Christopher Sible]

On RHEL7, kernel-ml-devel also gets kept. Should I add it to that list
too, or did you leave that off intentionally?

Joseph C. Sible

On Tue, 2020-01-28 at 09:11 -0800, Akemi Yagi wrote:
> On Tue, Jan 28, 2020 at 8:33 AM Joseph Christopher Sible
> <
> jcsible at cert.org
> > wrote:
> > 
> > I'm using kernel-ml on both RHEL7 and RHEL8 systems. On my RHEL7
> > systems, it works the way I want it to, which is also how the stock
> > kernels on both RHEL versions work: up to three of the kernel-ml
> > kernels exist at a time, and when yum updates them, it installs a new
> > kernel-ml package, and if there would be more than three, it also
> > uninstalls the oldest that isn't currently running.
> > 
> > However, on my RHEL8 systems, kernel-ml behaves like any other package:
> > there's only one of it at a time, and when yum updates it, the old one
> > is immediately overwritten, even if it's the running kernel. In
> > particular, this is a problem because once I install a kernel-ml
> > update, I can't load any new kernel modules until I reboot (since all
> > of the modules for my running kernel have been deleted). Is there a way
> > to get the other behavior back on RHEL8?
> > 
> > Joseph C. Sible
> 
> 
> We are aware of the issue and are working on it. There is a
> workaround. In the /etc/dnf/dnf.conf file, add a line:
> 
> installonlypkgs=kernel-ml kernel-ml-core kernel-ml-modules
> 
> then kernel-ml will be installed, not updated.
> 
> Akemi
> _______________________________________________
> elrepo mailing list
> elrepo at lists.elrepo.org
> 
> http://lists.elrepo.org/mailman/listinfo/elrepo
> 
>