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.
Description of problem:
grub lens does not handle "foreground" option
augeas-libs-1.0.0-5.el6_5.1.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Add something like this to your grub conf
default=0
timeout=5
foreground=ddb434
hiddenmenu
2. Run augtool to list title entries
augtool ls /files/etc/grub.conf/title
Actual results:
You get an empty list
Expected results:
You should get the list of entries configured in grub.conf
If you comment out the "foreground" option, everything works
Additional info:
The problem is in grub lens, because it handles the "background" option, but not "foreground"
It can be fixed just adding "foreground" option to the menu_settings
--- /usr/share/augeas/lenses/dist/grub.aug.orig 2014-01-29 18:17:37.319368496 +0000
+++ /usr/share/augeas/lenses/dist/grub.aug 2014-01-29 18:18:05.762706377 +0000
@@ -140,6 +140,7 @@
| kw_menu_arg "splashimage"
| kw_menu_arg "gfxmenu"
| kw_menu_arg "background"
+ | kw_menu_arg "foreground"
| serial
| terminal
| password_arg
It seems a quite harmless bug, but it makes virt-v2v fail when trying to migrate a VM with this option, that's how I traced this problem back to augeas...
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.
http://rhn.redhat.com/errata/RHBA-2014-1517.html
Description of problem: grub lens does not handle "foreground" option augeas-libs-1.0.0-5.el6_5.1.x86_64 How reproducible: Always Steps to Reproduce: 1. Add something like this to your grub conf default=0 timeout=5 foreground=ddb434 hiddenmenu 2. Run augtool to list title entries augtool ls /files/etc/grub.conf/title Actual results: You get an empty list Expected results: You should get the list of entries configured in grub.conf If you comment out the "foreground" option, everything works Additional info: The problem is in grub lens, because it handles the "background" option, but not "foreground" It can be fixed just adding "foreground" option to the menu_settings --- /usr/share/augeas/lenses/dist/grub.aug.orig 2014-01-29 18:17:37.319368496 +0000 +++ /usr/share/augeas/lenses/dist/grub.aug 2014-01-29 18:18:05.762706377 +0000 @@ -140,6 +140,7 @@ | kw_menu_arg "splashimage" | kw_menu_arg "gfxmenu" | kw_menu_arg "background" + | kw_menu_arg "foreground" | serial | terminal | password_arg It seems a quite harmless bug, but it makes virt-v2v fail when trying to migrate a VM with this option, that's how I traced this problem back to augeas...