Bug 1035825
| Summary: | Collect ovirt-engine runtime configuration files | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Lee Yarwood <lyarwood> | |
| Component: | ovirt-engine-log-collector | Assignee: | Sandro Bonazzola <sbonazzo> | |
| Status: | CLOSED ERRATA | QA Contact: | Petr Beňas <pbenas> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | high | |||
| Version: | 3.2.0 | CC: | acathrow, adahms, iheim, knesenko, kroberts, pstehlik, Rhev-m-bugs, scohen, yeylon | |
| Target Milestone: | --- | Keywords: | ZStream | |
| Target Release: | 3.4.0 | |||
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | integration | |||
| Fixed In Version: | ovirt-3.4.0-beta2 | Doc Type: | Bug Fix | |
| Doc Text: |
Previously, the rhevm-log-collector utility did not collect Red Hat Enterprise Virtualization Manager runtime configuration files. Now, these files are collected.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1060673 (view as bug list) | Environment: | ||
| Last Closed: | 2014-06-09 14:06:07 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | 1052854 | |||
| Bug Blocks: | 1060673, 1078909, 1142926 | |||
|
Description
Lee Yarwood
2013-11-28 15:09:29 UTC
(In reply to Lee Yarwood from comment #0) > Description of problem: > Collect ovirt-engine logging configuration files engine-service.xml.in & > engine-service-logging.properties.in > Aren't those files just templates? Why do you need them? (In reply to Sandro Bonazzola from comment #1) > (In reply to Lee Yarwood from comment #0) > > Description of problem: > > Collect ovirt-engine logging configuration files engine-service.xml.in & > > engine-service-logging.properties.in > > > > Aren't those files just templates? Why do you need them? Correct, these are templates but the logging configuration within these files is static and not updated by the ovirt-engine service script. We could fetch the complete configuration files from /var/tmp/ovirt-engine/ if you feel it makes more sense. (In reply to Lee Yarwood from comment #2) > > Aren't those files just templates? Why do you need them? > > Correct, these are templates but the logging configuration within these > files is static and not updated by the ovirt-engine service script. We could > fetch the complete configuration files from /var/tmp/ovirt-engine/ if you > feel it makes more sense. /var/tmp/ovirt-engine/config/ sounds better to me (should reflect the configuration really used right?) merged on upstream master, pushed to 3.4 branch. merged on upstream 3.4 branch. Verified in ovirt-log-collector-3.4.0-0.5.beta3.el6.noarch. [root@pb-rh34 tmp]# tar -tf sosreport-LogCollector-20140224142931.tar | grep '/var/tmp/ovirt-engine' ./pb-rh34-2014022414261393248410/var/tmp/ovirt-engine/ ./pb-rh34-2014022414261393248410/var/tmp/ovirt-engine/config/ ./pb-rh34-2014022414261393248410/var/tmp/ovirt-engine/config/ovirt-engine_history/ ./pb-rh34-2014022414261393248410/var/tmp/ovirt-engine/config/ovirt-engine_history/ovirt-engine.last.xml ./pb-rh34-2014022414261393248410/var/tmp/ovirt-engine/config/ovirt-engine_history/ovirt-engine.initial.xml ./pb-rh34-2014022414261393248410/var/tmp/ovirt-engine/config/ovirt-engine_history/current/ ./pb-rh34-2014022414261393248410/var/tmp/ovirt-engine/config/ovirt-engine_history/current/ovirt-engine.v1.xml ./pb-rh34-2014022414261393248410/var/tmp/ovirt-engine/config/ovirt-engine_history/ovirt-engine.boot.xml ./pb-rh34-2014022414261393248410/var/tmp/ovirt-engine/config/ovirt-engine-logging.properties ./pb-rh34-2014022414261393248410/var/tmp/ovirt-engine/config/ovirt-engine.xml 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-0668.html |