-
Notifications
You must be signed in to change notification settings - Fork 59
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
Fedora36 Next Auto-Upgrade Fails & Yields Grub Prompt #1149
Comments
Select details from the grub console gathered with @dustymabe: Initial failed boot message:
The results of
|
Yep. Basically what we saw was:
Since the So the question is: "How did the symlink manage to get messed up?" |
I'm not sure, but this looks like the boot filesystem was corrupted during the hard reset. So possibly an ext4 issue? At no point is |
Is there any code that creates a |
Describe the bug
Next node created on vSphere from OVA based on 35.20220313.1.0 with rpm-ostree-layered open-vm-tools failed to upgrade cleanly to 36.20220325.1.0. Identical sister node upgraded without issue.
Messages on the console seemed to indicate that kernel was found and a boot did commence but the machine did not come online from a network perspective. A hard reset of the VM via vSphere yielded the grub prompt.
Including systemd logs immediately prior to reboot into fedora36 in case these point to anything.
Reproduction steps
Unable to reproduce at this point.
System details
Systemd Logs Prior To Reboot
Top is latest timestamp.
The text was updated successfully, but these errors were encountered: