-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Work around initrd issue in sle11sp4 #888
Conversation
Are we sure the grub menu is incorrect right after the image has been created? IOW, I wonder whether the image is actually wrong or if we are updating the kernel for whatever reason, and it's the update that's gone wrong. |
If we need to hack something in the current sles11sp4 custom image, I would do it as earlier as possible, at the cloud-init stage. |
Yes, I loop-mounted the freshly downloaded qcow2, and the problem is already there. Thanks, that helps.
Nope, the image is already wrong. |
Why not, but an even better solution would be to directly fix image creation. The problem is, I'd like to test GMC now with a SLES 11 SP4 that survives a reboot. So I would suggest to apply this PR and remove it once we have something better. |
I failed trying to modify directly the image, ibs tool kills my workstation (freezing). I will apply this with big HACK signs. |
Reverted, I get a different image in CI than in my local tests... |
Is our mirror updated? |
Good question. I will give it a go again after next BV deployment. It could have been the mirror, it could be sumaform does differently when using the testsuite module or not, or it could have been me missing some point. |
What does this PR change?
This PR makes sure SLES 11 SP4 uses same version for kernel and kernel modules after a reboot.
A better solution would be to generate correct images. For more details, see #887.