Bug 672131 - Wrong method named in veritas.py
Wrong method named in veritas.py
Status: CLOSED UPSTREAM
Product: Fedora
Classification: Fedora
Component: sos (Show other bugs)
rawhide
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Jean-Francois Saucier
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2011-01-23 23:34 EST by Masatake YAMATO
Modified: 2011-03-21 19:33 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-03-21 19:33:13 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)
A patch fix the issue. (603 bytes, patch)
2011-01-23 23:34 EST, Masatake YAMATO
no flags Details | Diff

  None (edit)
Description Masatake YAMATO 2011-01-23 23:34:32 EST
Created attachment 474891 [details]
A patch fix the issue.

Description of problem:

While reading source code of sos, I've found a strange method name.
I think this will causes a bug.

`addcopyspec' method is invoked to collect /proc/sys/vxvm/vxio
in lib/sos/plugins/veritas.py. However, there is no such method
in source files in sosreport. Instead `addCopySpec' is defined and
used widly. 

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

the latest from svn repository.

How reproducible:

See lib/sos/plugins/veritas.py and search /proc/sys/vxvm/vxio.
You will see following line:

        self.addCopySpec("/proc/sys/vxvm/vxinfo")
        self.addcopyspec("/proc/sys/vxvm/vxio") <<<
        # vvr/svrm specific information
        self.addCopySpec("/etc/vx/vras")

Steps to Reproduce:
1.
2.
3.
  
Actual results:

addcopyspec.

Expected results:

addCopySpec.

Additional info:
Comment 1 Pierre Carrier 2011-03-21 19:33:13 EDT
Appeared in trunk but was never released, already removed as "/proc/sys" is included through system.py.

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