Red Hat Bugzilla – Bug 453792
sosreport fails to generate fdisk -l
Last modified: 2015-02-24 17:56:01 EST
Description of problem:
sosreport fails to generate fdisk -l unless a raid is present
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.run sosreport without a RAID present
2.verify that fdisk -l is not being generated.
fdisk -l is not being generated
fdisk -l is generated
Additional info: The cluster plugin also caused this to generated.
--- /usr/lib/python2.3/site-packages/sos/plugins/filesys.py 2008-07-02
+++ /usr/lib/python2.3/site-packages/sos/plugins/filesys.py2 2008-07-02
@@ -28,6 +28,7 @@
self.collectExtOutput("/bin/df -al", root_symlink = "df")
+ self.collectExtOutput("/sbin/fdisk -l", root_symlink = "fdisk_l")
self.collectExtOutput("/usr/sbin/lsof -b +M -n -l", root_symlink = "lsof")
self.collectExtOutput("/bin/mount -l", root_symlink = "mount")
"fdisk -l" was replaced by parted (and fdasd on s390s) as requested in bz453150. So what is really being fixed here is
"sosreport fails to generate _"partition table listing"_ unless a raid is present.
Hope this is ok with you, Robert, Jose.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.