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 1260555

Summary: grub2 shell function version_find_latest() failed to identify latest RHEL kernel
Product: Red Hat Enterprise Linux 7 Reporter: Till Maas <opensource>
Component: grub2Assignee: rmarshall
Status: CLOSED DUPLICATE QA Contact: Release Test Team <release-test-team-automation>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.3CC: toracat
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-10-12 18:34:44 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 Till Maas 2015-09-07 08:55:51 UTC
Description of problem:
grub2 uses a shell function called version_find_latest() to find the latest RHEL kernel. However sometimes it fails to identify the latest kernel resulting in an older kernel be booted instead of the latest one.

Version-Release number of selected component (if applicable):
grub2-tools-2.02-0.16.el7.x86_64


How reproducible:
always

Steps to Reproduce:
1. source /usr/share/grub/grub-mkconfig_lib  # get shell functions
2. version_find_latest /boot/vmlinuz-3.10.0-229.el7.x86_64 /boot/vmlinuz-3.10.0-229.11.1.el7.x86_64


Actual results:
/boot/vmlinuz-3.10.0-229.el7.x86_64

Expected results:
It should output the latest release, which is:
/boot/vmlinuz-3.10.0-229.11.1.el7.x86_64

Additional info:

Comment 2 Akemi Yagi 2015-09-14 12:26:15 UTC
I believe this is being addressed in BZ #1124074 and the fix is coming soon.

Comment 3 rmarshall 2015-10-12 18:34:44 UTC

*** This bug has been marked as a duplicate of bug 1124074 ***