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.
There's a problem with the package trigger for the grub2 plugin due to a change in packaging in RHEL8.
By default, we get 'lsinitrd' for the current initramfs image, and 'ls -lanR' for the entire '/boot' volume. This plugin also collects boot loader configuration for a number of legacy boot loaders that are no longer used in Red Hat products (milo, silo, elilo, yaboot).
If you are looking for configuration data for either the grub1 or grub2 boot loaders those are captured by their own plugins (grub and grub2 resp.):
# sosreport -v --batch --build --profile=boot
sosreport (version 3.6)
[...]
sosreport build tree is located at : /var/tmp/sosreport-localhost-2019-01-15-roadowq
# ls sosreport-localhost-2019-01-15-roadowq/boot
boom efi grub2 loader
# ls sosreport-localhost-2019-01-15-roadowq/boot/grub2/
grub.cfg grubenv
# ls -l sosreport-localhost-2019-01-15-roadowq/etc/grub2.cfg
lrwxrwxrwx. 1 root root 22 Jan 15 10:31 sosreport-localhost-2019-01-15-roadowq/etc/grub2.cfg -> ../boot/grub2/grub.cfg
Generally, if you're just interested in boot-relevant data use the 'boot' profile, rather than just the 'boot' plugin.
Looking on a RHEL8 system, it seems that there is no longer a 'grub2' package installed by default; this means that the trigger for the plugin does not fire, and that is the reason you don't find the other data in the report.
We need to add 'grub2-common' to the package list for the plugin, since this is always installed on RHEL8 machines using grub2:
class Grub2(Plugin, RedHatPlugin, DebianPlugin, UbuntuPlugin):
"""GRUB2 bootloader
"""
plugin_name = 'grub2'
profiles = ('boot',)
packages = ('grub2', 'grub2-efi', 'grub2-common')
To test, you can either make this change to the plugin file locally, or force-enable the plugin with '-e grub2'.
There's a problem with the package trigger for the grub2 plugin due to a change in packaging in RHEL8. By default, we get 'lsinitrd' for the current initramfs image, and 'ls -lanR' for the entire '/boot' volume. This plugin also collects boot loader configuration for a number of legacy boot loaders that are no longer used in Red Hat products (milo, silo, elilo, yaboot). If you are looking for configuration data for either the grub1 or grub2 boot loaders those are captured by their own plugins (grub and grub2 resp.): # sosreport -v --batch --build --profile=boot sosreport (version 3.6) [...] sosreport build tree is located at : /var/tmp/sosreport-localhost-2019-01-15-roadowq # ls sosreport-localhost-2019-01-15-roadowq/boot boom efi grub2 loader # ls sosreport-localhost-2019-01-15-roadowq/boot/grub2/ grub.cfg grubenv # ls -l sosreport-localhost-2019-01-15-roadowq/etc/grub2.cfg lrwxrwxrwx. 1 root root 22 Jan 15 10:31 sosreport-localhost-2019-01-15-roadowq/etc/grub2.cfg -> ../boot/grub2/grub.cfg Generally, if you're just interested in boot-relevant data use the 'boot' profile, rather than just the 'boot' plugin. Looking on a RHEL8 system, it seems that there is no longer a 'grub2' package installed by default; this means that the trigger for the plugin does not fire, and that is the reason you don't find the other data in the report. We need to add 'grub2-common' to the package list for the plugin, since this is always installed on RHEL8 machines using grub2: class Grub2(Plugin, RedHatPlugin, DebianPlugin, UbuntuPlugin): """GRUB2 bootloader """ plugin_name = 'grub2' profiles = ('boot',) packages = ('grub2', 'grub2-efi', 'grub2-common') To test, you can either make this change to the plugin file locally, or force-enable the plugin with '-e grub2'.