Bug 1173766

Summary: [RFE] log collector should collect engine-config settings and domain information
Product: Red Hat Enterprise Virtualization Manager Reporter: Jake Hunsaker <jhunsaker>
Component: ovirt-log-collectorAssignee: Scott Herold <sherold>
Status: CLOSED ERRATA QA Contact: Gonza <grafuls>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.4.4CC: amureini, gklein, iheim, lpeer, lsurette, oourfali, pstehlik, rbalakri, Rhev-m-bugs, sbonazzo, yeylon, ykaul
Target Milestone: ovirt-3.6.0-rcKeywords: FutureFeature
Target Release: 3.6.0Flags: sherold: Triaged+
Hardware: x86_64   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-03-09 19:59:40 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Integration RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1234855    

Description Jake Hunsaker 2014-12-12 21:43:41 UTC 
Description of problem:

Currently sos/log-collector does not capture engine-config values or domain information.

We should capture both of these as the tunables can help in troubleshooting.
Similarly the domain information can help track AD/IPA issues.

These can currently be dug out from the DB dump, however having them in a plaintext file makes checking these much faster and easier, and a DB is not always available.

Version-Release number of selected component (if applicable):
rhevm-log-collector-3.4.5-1.el6ev.noarch

How reproducible:
Always


Actual results:

engine-config and engine-manage-domains output is not collected.

Expected results:

This information should be collected.

Additional info:

http://gerrit.ovirt.org/#/c/36116/
Comment 1 Gonza 2015-07-07 12:19:52 UTC 
Verified with:
ovirt-log-collector-3.6.0-0.1.master.20150528070835.git82e9694.el6.noarch
sos-3.2-28.el6.noarch
Comment 4 errata-xmlrpc 2016-03-09 19:59:40 UTC 
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/RHEA-2016-0392.html