Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Document URL:
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7-Beta/html/System_Administrators_Guide/sec-Upgrading_from_GRUB_Legacy_to_GRUB2.html
Section Number and Name:
25.8. UPGRADING FROM GRUB LEGACY TO GRUB2
Describe the issue:
- The "Prerequisites for upgrading" sub-section contains three steps. But
it is not clear, whether it is prerequisite for upgrading of the system
or upgrade of the GRUB. The step 1 should be done before the upgrade of
the system, however steps 2) and 3) should be done on the upgraded system
(that means on the RHEL 7 system).
- Since RHEL 7.4, the grub2 package is not installed automatically so the
paragraph in step three is confusing for some users. Actually, the text below
the step 3 has different indentation so it seems like it is not part of the
step 3 actually. The sentence of the step 3 doesn't make sense at all as
it says:
"Your RHEL system that has been upgraded from version 6 to 7"
But the system should be already upgraded before the step 2.
- In addition, since RHEL 7.4 grub-legacy will be possibly still installed
(depends on more things) on the new system.
Suggestions for improvement:
Clarify which steps are supposed to be done on the old system before the
in-place upgrade and which should be done on the new upgraded system.
Modify text for steps 2 and 3, so it will not matter whether packages are
already installed on the new system or not. Something like:
Be sure that you have installed these packages and in case they are missing,
install them manually:
...
Additional information: