Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 451679

Summary: sosreport does not capture elilo.conf
Product: Red Hat Enterprise Linux 5 Reporter: Rick Beldin <rick.beldin>
Component: sosAssignee: Adam Stokes <astokes>
Severity: medium Docs Contact:
Priority: low    
Version: 5.2CC: agk, bmr
Target Milestone: rc   
Target Release: ---   
Hardware: ia64   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-06-16 17:45:58 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Description Flags
sosreport from a HP Integrity rx2660 with RHEL5.2 none

Description Rick Beldin 2008-06-16 17:18:16 UTC
Description of problem:  On ia64, sosreport does not capture the elilo.conf,
often a necessary piece of information in troubleshooting customer systems. 

In sosreport;s output in sosreport/sos_commands/bootloader we have two 



lilo_-q is obviously incorrect on ia64: 
 /bin/sh: /sbin/lilo: No such file or directory

The ls_-laR.boot is more useful, but does not contain the *contents* of the
elilo.conf.   Seems like a 'find' command coupled with a cat could fix this. 

Version-Release number of selected component (if applicable):


How reproducible:

Every time

Steps to Reproduce:
1. run sosreport
2. look for elilo.conf information
3. fail to find it ;-) 
Actual results:

Expected results:

Additional info:

Something similar could be done for grub on other platforms.

Comment 1 Rick Beldin 2008-06-16 17:18:16 UTC
Created attachment 309518 [details]
sosreport from a HP Integrity rx2660 with RHEL5.2

Comment 2 Adam Stokes 2008-06-16 17:45:58 UTC

*** This bug has been marked as a duplicate of 337901 ***