I had some RHEL 8 machines break after installing 4.18.0-553.50. I went to check on my Rocky 8 VMs and saw that they were still on 4.18.0-553.47, and that .50 hadn’t become available yet. My first thought was that the problem with .50 on RHEL is specific to my hosting provider, but now I’m wondering if Rocky caught a problem with this kernel and is holding it back. Does anyone know of any problems with with kernel 4.18.0-553.50?
As a more general question, does Rocky Linux hold off on releasing packages if it has already been released on RHEL and is known to cause problems?
Our kernels require to be built in a secure boot environment. This increases the time it takes for us to release them. We also had to renew our secure boot certificates recently, so as a result, more vetting is required before we can give it the OK to release to our mirrors.
This is a VM running on VMware ESXi and boots into that kernel perfectly fine. I can check on my other server which is running Rocky 9 and KVM and create a VM there to see if it works with that kernel or not although I expect it would.
It would be interesting/nice to know the reason why it doesn’t work at your hosting provider. At least that way we can find out what the problem is.
EDIT:
yes, works on KVM as well, so it would seem your hosting provider has a problem with that particular kernel.