Red Hat Bugzilla – Bug 977187
sosreport should capture /etc/yaboot.conf as well as /boot/yaboot.conf
Last modified: 2016-04-18 06:25:20 EDT
Description of problem:
sosreport on powerpc hardware takes a copy of /boot/yaboot.conf, but not /etc/yaboot.conf which is often more important. It may depend on RHEL version, but I believe /boot/yaboot.conf is sometimes just a copy of the master /etc/yaboot.conf, necessary with some /boot configurations. This information can be vital for debugging powerpc boot problems
Version-Release number of selected component (if applicable):
But same in current sources, afaict.
Steps to Reproduce:
1. Run sosreport on powerpc hardware
Generated report contains /boot/yaboot.conf (if present) but not /etc/yaboot.conf
Report contains both /etc/yaboot.conf and /boot/yaboot.conf (if present).
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux release. Product Management has
requested further review of this request by Red Hat Engineering, for
potential inclusion in a Red Hat Enterprise Linux release for currently
deployed products. This request is not yet committed for inclusion in
Wasn't this a symlink at some point (mirroring grub.conf)?
I'm happy to put this in 5.10 as long as we get the acks.
It may have been, but I've hit at least one case where it's not. So, it would be good to get both versions just in case. If we grabbed a stat so the sosreport shows if it is a symlink or not would be even better, I guess.
$ cat sos-bz977187-add-etc-yaboot.patch
diff -up sos-1.7/lib/sos/plugins/bootloader.py.orig sos-1.7/lib/sos/plugins/bootloader.py
--- sos-1.7/lib/sos/plugins/bootloader.py.orig 2013-07-24 13:27:33.205291609 +0100
+++ sos-1.7/lib/sos/plugins/bootloader.py 2013-07-24 13:27:41.802324881 +0100
@@ -25,6 +25,7 @@ class bootloader(sos.plugintools.PluginB
self.collectExtOutput("/bin/ls -laR /boot")
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.