Description of problem: /var/log/sanlock.log is useful for debugging sanlock problems. Version-Release number of selected component (if applicable): rhevm-log-collector-3.1.0-10.el6ev.noarch sos-2.2-38.el6.noarch
Created attachment 774659 [details] Patch to add sanlock.py in vdsm plugin of sosreport
(In reply to Humble Chirammal from comment #1) > Created attachment 774659 [details] > Patch to add sanlock.py in vdsm plugin of sosreport The patch should collect that information. I will push that to upstream/downstream soon.
*** Bug 985216 has been marked as a duplicate of this bug. ***
vdsm 3.2 obsoletes 3.1.z - removing 3.1.z flag also, iiuc patch is in vdsm side, not log collector side - changing component.
I'm a bit unclear on the lifetimes for the RHEV products. We are still supporting customers with RHEV 3.1, and this logcollector fault makes it more difficult, so why are we removing 3.1.z target?
fixed. log collector collects sanlog.log from hosts.
This bug is currently attached to errata RHBA-2013:15291. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance.
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. http://rhn.redhat.com/errata/RHBA-2014-0040.html