Bug 451679 - sosreport does not capture elilo.conf
sosreport does not capture elilo.conf
Status: CLOSED DUPLICATE of bug 337901
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: sos (Show other bugs)
5.2
ia64 Linux
low Severity medium
: rc
: ---
Assigned To: Adam Stokes
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-06-16 13:18 EDT by Rick Beldin
Modified: 2008-06-16 13:45 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-06-16 13:45:58 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
sosreport from a HP Integrity rx2660 with RHEL5.2 (1.59 MB, application/x-bzip2)
2008-06-16 13:18 EDT, Rick Beldin
no flags Details

  None (edit)
Description Rick Beldin 2008-06-16 13:18:16 EDT
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 
files: 

lilo_-q  

ls_-laR_.boot

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):

sos-1.7-9.2.el5

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 13:18:16 EDT
Created attachment 309518 [details]
sosreport from a HP Integrity rx2660 with RHEL5.2
Comment 2 Adam Stokes 2008-06-16 13:45:58 EDT

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

Note You need to log in before you can comment on or make changes to this bug.