Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1706094
Summary: | Failed to keep volume group name during upgrade | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | developer <developer> |
Component: | fedora-upgrade | Assignee: | Miroslav Suchý <msuchy> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 30 | CC: | cheese, msuchy |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-05-07 08:04:33 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
developer@typeset.net
2019-05-03 14:26:26 UTC
See https://fedoraproject.org/wiki/Common_F30_bugs#GRUB_boot_menu_is_not_populated_after_an_upgrade *** This bug has been marked as a duplicate of bug 1652806 *** I really don't think this is the same bug. Here are some of the reasons I believe it isn't: 1) The grub entries WERE populated in the grub configuration, it was able to boot with the updated grub entry. It only failed to complete the boot while looking for the root filesystem. (wasn't able to find it because it had a misnamed volume group entry) 2) BUG 1652806 appears to be non-EFI boot issues. My issue is EFI boot. And the issue wasn't a corrupt grub config, or grub config missing boot entries. Upgrade process had modified /etc/default/grub and changed the root volume group from mine to a default "fedora" entry It is interesting that it happened during the upgrade of Fedora 30, I didn't have this issue when I upgraded to 29. |