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.

Bug 1497731

Summary: During the upgrade from RHEL-6.9 to RHEL-7.4 no grub2 package is installed.
Product: Red Hat Enterprise Linux 6 Reporter: Peter Kotvan <pkotvan>
Component: preupgrade-assistant-el6toel7Assignee: Petr Stodulka <pstodulk>
Status: CLOSED ERRATA QA Contact: Tereza Cerna <tcerna>
Severity: medium Docs Contact: Jiri Hornicek <jhornice>
Priority: medium    
Version: 6.9CC: dwojewod, jhornice, jmazanek, mateusz.bacal, mlinden, ovasik, phracek, pstodulk, tcerna
Target Milestone: rcKeywords: Extras, Reopened
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: preupgrade-assistant-el6toel7-0.7.0-1.el6 Doc Type: Bug Fix
Doc Text:
Starting with Red Hat Enterprise Linux 7.4, the grub2 RPM package stopped obsoleting the grub package after the upgrade of the source system. As a consequence, the grub2 package was not installed on the target system automatically. With this update, the postupgrade script was added to ensure that the grub2 package is installed on the target system, which is the expected scenario.
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-11-14 20:40:58 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 Peter Kotvan 2017-10-02 14:21:39 UTC
Description of problem:
I've installed  a server variant of RHEL-6.9 system on x86_64 machine with a default package set. I performed the upgrade to RHEL-7.4. After the installation there were no grub2 packages installed. The system booted with legacy grub as expected and described in the documentation.

Version-Release number of selected component (if applicable):
redhat-upgrade-tool-0.7.50-1.el6
RHEL-6.9 -> RHEL-7.4

How reproducible:
always

Steps to Reproduce:
1. Install RHEL-6.9 / Server / x86_64 with default package set.
2. Install the preupgrade-assistant and redhat-upgrade-tool.
3. Perform the upgrade by running preupg and redhat-upgrade-tool-cli --iso=RHEL-7.4.iso
4. After the last reboot log in to installed system and check if there is a grub2 package installed: $ rpm -qa | grub2

Actual results:
grub2 packages are not installed after the upgrade from RHEL-6.9 to RHEL-7.4.

Expected results:
grub2 packages are installed after the upgrade.


Additional info:

Comment 1 msi_bacalm 2017-10-03 05:52:01 UTC
Hi,

I agree that this is separate bug.

Based on your comment 
"actually the grub and grub2 packages behave differently and are not upgraded. This does not necessarily depend on an obsolete clause in the package." - that is not fully true - redhat upgrade tool when I turned on debug logs I noticed that he is performing dummy yum transaction check based on which he is discovering what packages need to be installed on upgrade - at least this is my opinion.

When I compared the same output I noticed that on upgrades 6.9 -> 7.3 transaction showing that grub is obsoleted by grub2. In that scenario I have installed grub2. 

Unfortunately on upgrade 6.9 -> 7.4 I do not have one....

For now I was able to workaround it by adding postupgrade script which will remove legacy grub and install grub2. I have separated script which is handling migration.

So I am not sure whether this is issue with preupgrade-assistant packages rather change on behavior of grub2 which is no longer obsoleting grub....

Comment 2 Petr Stodulka 2017-10-03 07:49:24 UTC
Hi,
installed grub2 or not, from my point of view it doesn't matter. Installed
package doesn't mean anything when it is not used. And after upgrade,
originally the grub was removed and the grub2 was installed, but still the grub
was used. Not the grub2. Even, in case of troubles, you would have more troubles 
because of missing the grub-legacy. That's why you need back up the rpm file 
manually and force installation of the grub-legacy after in-place upgrade (and normal installation of the grub2) during your manual migration from grub-legacy to grub2.

Comment 3 msi_bacalm 2017-10-03 08:22:19 UTC
Hi,

We are taking over migration from grub-legacy to grub2, but the main point of this bugzilla is that after upgrade there is no grub2 which as I quoted was mention in document.

Yes I see that you mention that after upgrade you might need to install it manually. In my opinion this is kind of safe zone for redhat to avoid issue like this one with grub which in that case shall some somehow resolved to take care of installation of grub2 - useers of redhat will take care of removing and migrating from legacy grub.

Comment 4 Petr Stodulka 2017-10-03 08:50:02 UTC
For the document is reported bug 1497762 since yesterday. I guess the document
will be modified possibly earlier than the new modules will be released. Even when it is mentioned inside the article, there is mentioned even command you should use to install grub2 package in case it is not installed.

Probably we can still try to install the grub2 during post-upgrade phase, so it will be installed on the upgraded machine.

Comment 5 msi_bacalm 2017-10-03 08:53:16 UTC
Hi

"Probably we can still try to install the grub2 during post-upgrade phase, so it will be installed on the upgraded machine." 

Yes, this exactly what I was looking for ;)

For now I workaround it exactly by installing grub2 in postupgrade. ;)

I would like to keep this bugzilla open for tracking this change, are you with this ?

Comment 6 Petr Stodulka 2017-10-03 08:57:37 UTC
Yes, in that case you can keep it opened for tracking :)

Comment 7 msi_bacalm 2017-10-03 08:59:00 UTC
Thanks ;)

Comment 8 msi_bacalm 2017-10-03 08:59:44 UTC
BTW is there any planned date when we might expect to have this implemented ?

Comment 9 Petr Stodulka 2017-10-03 09:15:03 UTC
Nothing what I can share. But you can track the upstream [0] repository
to see when it is part of the upstream already.

[0] https://github.com/upgrades-migrations/preupgrade-assistant-modules

Comment 10 Petr Stodulka 2017-10-20 10:13:31 UTC
The fix will be part of modules v0.7.0 and higher.
  See PR: https://github.com/upgrades-migrations/preupgrade-assistant-modules/pull/26

Comment 11 msi_bacalm 2017-10-20 10:22:51 UTC
Great ;),

what is the schedule of releasing this via redhat website ?

Comment 12 Petr Stodulka 2017-10-20 19:55:27 UTC
It will be part of next release. That's all I can say.

Comment 14 Alois Mahdal 2017-10-23 09:25:49 UTC
Notes for QE
============

Already covered in test suite; so just make sure #561715 /CoreOS/preupgrade-assistant-el6toel7/upg/grub2-package-after-upgrade passes.  (It's part of pa67-r-upg-ours and tiet3 in ipu 0.1.2)

Comment 15 Tereza Cerna 2017-11-07 11:55:57 UTC
Test passed. 
-> VERIFIED

Comment 17 errata-xmlrpc 2017-11-14 20:40:58 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:3212