Bug 1420749
Summary: | Incorrect ordering of boot menu entries generated by grubby | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Jaroslav Reznik <jreznik> | ||||||||||
Component: | grubby | Assignee: | rmarshall | ||||||||||
Status: | CLOSED ERRATA | QA Contact: | Release Test Team <release-test-team-automation> | ||||||||||
Severity: | high | Docs Contact: | |||||||||||
Priority: | urgent | ||||||||||||
Version: | 7.2 | CC: | asanders, bs168, cww, fkrska, jstodola, jvavra, kdixon, ktordeur, lkimlick, mbanas, mschena, pjones, rbeyel, rmarshall, srandhaw, syangsao | ||||||||||
Target Milestone: | rc | Keywords: | ZStream | ||||||||||
Target Release: | --- | ||||||||||||
Hardware: | Unspecified | ||||||||||||
OS: | Unspecified | ||||||||||||
Whiteboard: | |||||||||||||
Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||||
Doc Text: | Story Points: | --- | |||||||||||
Clone Of: | 1285601 | Environment: | |||||||||||
Last Closed: | 2017-04-12 12:37:13 UTC | Type: | --- | ||||||||||
Regression: | --- | Mount Type: | --- | ||||||||||
Documentation: | --- | CRM: | |||||||||||
Verified Versions: | Category: | --- | |||||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
Embargoed: | |||||||||||||
Bug Depends On: | 1285601 | ||||||||||||
Bug Blocks: | |||||||||||||
Attachments: |
|
Description
Jaroslav Reznik
2017-02-09 13:01:32 UTC
Created attachment 1261521 [details]
/etc/zipl.conf before installing new kernel
Created attachment 1261522 [details]
/etc/zipl.conf after installing new kernel
Created attachment 1261523 [details]
/var/log/grubby
Created attachment 1261524 [details]
/var/log/grubby_prune_debug
Retested with grubby-8.28-21.el7_3 and this bug is fixed. The default boot entry "without debugging" doesn't contain any debug boot parameters and it's above the entry "with debugging". Tested on x86_64, ppc64, ppc64le and s390x. Moving to VERIFIED. 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:0921 |