DescriptionBranislav Náter
2016-04-06 14:45:04 UTC
Description of problem:
When using lvmdump=on (or lvmdump-am=on) options from lvm2 plugin, expected data are not collected.
Version-Release number of selected component (if applicable):
sos-3.2-40.el6
How reproducible:
always
Steps to Reproduce:
1. sosreport -o lvm2 --tmp-dir=. --batch -k lvm2.lvmdump=on
Actual results:
no data in sos_commands/lvm2/lvmdump/ directory
Expected results:
Expected data are present
Additional info:
When running lvmdump command and providing directory where to dump data (using -d <dirname> switch), directory should not exists. Otherwise lvmdump exits with error: "Fatal: <dirname> already exists"
When running lvmdump in lvm2 plugin, get_cmd_output_path() method from __init__.py is used:
cmd = lvmdump_cmd % (lvmdump_opts,
self.get_cmd_output_path(name="lvmdump")) <--------
self.add_cmd_output(cmd)
This method creates provided directory "lvmdump" and that cause lvmdump command to fails.
Fix is as easy as run get_cmd_output_path() with "make=False" argument to prevent directory creation:
cmd = lvmdump_cmd % (lvmdump_opts,
self.get_cmd_output_path(name="lvmdump", make=False)) <--
self.add_cmd_output(cmd)
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.
https://rhn.redhat.com/errata/RHBA-2017-0695.html