Bug 1229341
Summary: | system/grub: Minor rewrite | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Alois Mahdal <amahdal> |
Component: | preupgrade-assistant-el6toel7 | Assignee: | Petr Stodulka <pstodulk> |
Status: | CLOSED ERRATA | QA Contact: | Alois Mahdal <amahdal> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.7 | CC: | deekej, jhornice, msvistun, ovasik, phracek, pjones, pstodulk, rstrode, ttomecek |
Target Milestone: | rc | Keywords: | Extras |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | preupgrade-assistant-el6toel7-0.6.59-1.el6 | Doc Type: | Enhancement |
Doc Text: |
Previously, the "GRUB to GRUB2 migration" module contained only the information about the fix enabling the modification of boot parameters. With this update, the information about expected manual actions after the in-place upgrade has been added.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2016-11-04 08:59:53 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: | |||
Bug Depends On: | |||
Bug Blocks: | 1335038 |
Description
Alois Mahdal
2015-06-08 13:47:43 UTC
"Fixed In Version" was set in error. New text says:
> The file splash.xpm.gz allows you to modify boot parameters during the booting.
Is this really true? splash.xpl.gz is nothing but a bitmap; it does not "allow" you to do it.
The original text was already misleading; I'm not sure what orignal author meant, but absence of a mere bitmap should not prevent you from changing that (unless what they meant is that there is a bug in some auxiliary tool; in that case it should be meant clear.)
Peto, can You clarify it? I am not so familiar with GRUB here. Well, we have realized a time ago, if file is missing then we are not able to update/delete/add grub menu options. That's all. Absence of bitmap really prevent changing grub options. (In reply to Petr Hracek from comment #8) > Well, we have realized a time ago, if file is missing then we are not able > to update/delete/add grub menu options. > > That's all. Absence of bitmap really prevent changing grub options. Seems to me as what I mentioned above: there is a bug/limitation in some auxiliary tool we happen to use ... I can't imagine other way. Can you confirm that? Does that mean that people who don't (want to) use GRUB bitmap at all are out of luck? I think it sounds silly just saying that bitmap enables you to change settings--that just does not make sense; we should be more specific. (Also I have a (Debian) machine with GRUB w/o bitmap and I'm sure I have changed settings there) Hi David, I have a question. During an in-place upgrade we have to backup file /etc/grub/splash.xpm.gz. Without them, we are not able to edit grub configuration line over boot menu. File is owned by redhat-logos package. On RHEL-6 redhat-logos package owns the file splash.xpm.gz. Unfortunately redhat-logos disappear from package redhat-logos on RHEL-7. Is this a bug for grub? Relevant old BZ is: https://bugzilla.redhat.com/show_bug.cgi?id=1146537 Can you please look at it? Why are we not able to edit grub configuration line during boot if file does not exist? Can you please give us an overview, why splash.xpm.gz disappear? It wasn't getting installed in a place grub2 would look for it (see bug 1063246), and it isn't getting used anyway, since we don't want a splash at the bootloader menu ( see bug 1003873 comment 1 ) Does it also mean, grub is replaced by grub2 in case of upgrade RHEL-6 -> RHEL-7? Or grub remains as a bootloader on RHEL-7 instead of grub2? not sure. Peter would know. AFAIK inplace upgrade still uses grub instead of grub2 on RHEL-7 and manual steps from user are required after upgrade to install and configure grub2 completely, because we can't cover all possible changes automatically. This produced several bugs already over time, including troubles with grubby and our workround where we modify config file automatically due to crash of grubby. Is it answer on your question? More issues have been identified: * Texts and meta-data focus on splash.xpm, instead of explaining that the GRUB part of upgrade has to be done manually. * Module would signalize 'pass' if splash.xpm.gz did not exist on the old system. While not sure if this is likely, it would be incorrect as manual steps are needed always. Latest patch (already included in build now in Fixed In Version field) brings following changes: * Texts and meta-data now explain situation in full extent. * The splash.xpm.gz risk has been removed; instead the issue (which we can easily work around) is mentioned as part of solution text. * New unconditional risk has been added to call attention to the need of manual steps. Changing the focus of this bug. Tested with preupgrade-assistant-el6toel7-0.6.59-3.el6. The system/grub module will now always contain updated text and (medium) risk, clearly explaining the situation including steps to be done. The module result is needs_inspection. 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://rhn.redhat.com/errata/RHEA-2016-2618.html |