Bug 1085040

Can you attach the grub.cfg from before and after the upgrade, as well as /var/log/redhat_upgrade_tool.log and /var/log/upgrade.log?

will attach those files. I actually wouldn't be surprised if this is caused by bug 1062714  .  the upgrade left me with broken python.

Created attachment 883694 [details]
old grub.conf

Created attachment 883695 [details]
new grub.conf

Created attachment 883696 [details]
redhat-upgrade-tool log

Created attachment 883697 [details]
upgrade.log

This is similar to bug 1062714, but yum appears to be making some decisions that don't make any sense. The logs indicate grubby-7.0.15-5.el6.x86_64 is being upgraded to grubby-8.28-8.el7.x86_64, but then there's:

[   151.433] (DD) redhat_upgrade_tool.depsolve:format_missing_requires() MISSING REQ: kernel-2.6.32-358.14.1.el6.x86_64 requires /sbin/new-kernel-pkg
[   151.436] (DD) redhat_upgrade_tool.yum:_requiringFromTransaction() TSINFO: Marking grubby-7.0.15-5.el6.i686 as install for kernel-2.6.32-358.14.1.el6.x86_64

The kernel package is being removed, so I assume it's for the preun dependency, but the dependencies in the rpm are for  grubby >= 7.0.4-1 and /sbin/new-kernel-pkg, both of which are provided by grubby-8.28-8. Unless this is related to UsrMove, I guess, but the RHEL 7 kernel.spec still uses /sbin and not /usr/sbin as the dependency.

Reassigning to yum.

> The kernel package is being removed, so I assume it's for the preun
> dependency, but the dependencies in the rpm are for  grubby >= 7.0.4-1 and
> /sbin/new-kernel-pkg, both of which are provided by grubby-8.28-8. Unless
> this is related to UsrMove, I guess, but the RHEL 7 kernel.spec still uses
> /sbin and not /usr/sbin as the dependency.

 8.28 doesn't provide that.

% rpm -qlp 7.0.15/5.el6/i686/grubby-7.0.15-5.el6.i686.rpm
/sbin/grubby
/sbin/installkernel
/sbin/new-kernel-pkg
/usr/share/doc/grubby-7.0.15
/usr/share/doc/grubby-7.0.15/COPYING
/usr/share/man/man8/grubby.8.gz
/usr/share/man/man8/installkernel.8.gz
/usr/share/man/man8/new-kernel-pkg.8.gz
% rpm -qlp 8.28/8.el7/i686/grubby-8.28-8.el7.i686.rpm
/usr/sbin/grubby
/usr/sbin/installkernel
/usr/sbin/new-kernel-pkg
/usr/share/doc/grubby-8.28
/usr/share/doc/grubby-8.28/COPYING
/usr/share/man/man8/grubby.8.gz
/usr/share/man/man8/installkernel.8.gz
/usr/share/man/man8/new-kernel-pkg.8.gz
% rpm -qp --provides 8.28/8.el7/i686/grubby-8.28-8.el7.i686.rpm
grubby = 8.28-8.el7
grubby(x86-32) = 8.28-8.el7


> 
> Reassigning to yum.

James, did you mean to close this as NOTABUG versus move it to grubby?

to be clear the bug (is the very serious iss) "RHEL6 to RHEL7 upgrade doesn't work".  Do you believe that problem to be gone?

Are you were you just looking at this report through yum goggles ?

During the upgrade RHEL6.6->RHEL7.1 the grub.conf loses the initrd again.
Reopen the bug.

It causes kernel panic.

Created attachment 947668 [details]
audit.log

Yes, it seems that this could be source of problems. grubby is indirectly dependent on cyrus-sasl-lib, which contains libsasl2.so*
(see for rhel-7: repoquery -R --resolve --recursive grubby | grep -i cyrus).

Change component to cyrus-sasl-lib.

Based on my analysis for issue occuring in 7.1 seems to be a regression in grubby.

This line from postrans of kernel package:

/usr/sbin/new-kernel-pkg --package kernel --mkinitrd --dracut --depmod --update 3.10.0-201.el7.x86_64 || exit $?

initiates different grubby commands (those updating grub.cfg) with packages from 7.0 and 7.1

With grubby-8.28-11.el7.x86_64 (version from RHEL-7.1) new-kernel-pkg mentioned above uses this to update the grub.cfg:

/sbin/grubby --grub -c /boot/grub/grub.conf --update-kernel=/boot/vmlinuz-3.10.0-201.el7.x86_64 --initrd /boot/initramfs-3.10.0-201.el7.x86_64.img --args=" LANG=en_US.UTF-8" --title="Red Hat Enterprise Linux Server (3.10.0-201.el7.x86_64) 7.1 (Maipo)$debugtitle"

While with grubby-8.28-8.el7.x86_64 (version from RHEL-7.0) command is:

/sbin/grubby --grub -c /boot/grub/grub.conf --update-kernel=/boot/vmlinuz-3.10.0-201.el7.x86_64 --initrd /boot/initramfs-3.10.0-201.el7.x86_64.img --args=" LANG=en_US.UTF-8"

The only difference is in --title option. I manually verified on RHEL-7.1 got by Inplace upgrade that --title does the magic. When defined the grubby does not update grub.cfg, while without --title it does the thing.

It's good idea to repeat that described issue happens after RHEL-7 Inplace upgrade when RHEL-6.6 is updated to RHEL-7.1 which always keeps _grub_  in use also on RHEL-7 (not the grub2 as usual), thus this is all about configuring grub-0.97 on RHEL-7.

Finally as Juraj Marko mentioned, this is blocker and TestBlocker for RHEL7 Inplace Upgrades feature as the system can not boot after inplace upgrade unless grub configuration is manually updated.

Please open each of these issues as an individual bug.  It looks like the original problem here is not currently able to be reproduced, and it's impossible to tell which (if any) followup bug should be addressed, so I'm NAKing this bug.

let's clean the needinfo, I guess this one probably should be either closed or reassigned, as grubby only part was already entered separately.

yea let's close this out for clarity sake