Description of problem: When rhevm-reports is installed, placing /etc/ovirt-engine/engine.conf.d/50-redhat-support-plugin.conf (ENGINE_APPS="${ENGINE_APPS} redhat-support-plugin-rhev.ear"). parser dereference ENGINE_APPS in a recursion: ${ENGINE_APPS} rhevm-reports.war rhevm-reports.war rhevm-reports.war ..... So log collector enters infinite loop, consuming 100% CPU. Version-Release number of selected component (if applicable): IS19 How reproducible: 100% Steps to Reproduce: 1. install rhevm + dwh + reports 2. run log collector utility 3. Actual results: Tool enters infinite loop Expected results: logs collection Additional info:
patch merged upstream master, pushed to 3.3 branch.
patch merged upstream 3.3 branch.
Verified on RHEVM 3.3 IS21.
Verification failed on IS21: # rpm -q rhevm-log-collector rhevm-log-collector-3.3.1-2.el6ev.noarch # rpm -qa | egrep 'report|dwh' rhevm-dwh-3.3.0-18.el6ev.noarch rhevm-reports-3.3.0-18.el6ev.noarch jasperreports-server-pro-5.5.0-4.el6ev.noarch # date Thu Nov 7 14:53:46 IST 2013 [root@fire33-vdc ~]# rhevm-log-collector # date Thu Nov 7 14:54:08 IST 2013
It's fixed in IS22.
Verified on RHEVM 3.3 IS22: #rpm -q rhevm-log-collector rhevm-log-collector-3.3.1-3.el6ev.noarch # rpm -qa | egrep 'report|dwh' rhevm-dwh-3.3.0-19.el6ev.noarch rhevm-reports-3.3.0-19.el6ev.noarch jasperreports-server-pro-5.5.0-4.el6ev.noarch #rpm -qa | grep redhat-support* redhat-support-plugin-rhev-3.3.0-11.el6ev.noarch # engine-log-collector collect INFO: Gathering oVirt Engine information... INFO: Gathering PostgreSQL the oVirt Engine database and log files from localhost... Please provide the REST API password for the admin@internal oVirt Engine user (CTRL+D to skip): INFO: No hypervisors were selected, therefore no hypervisor data will be collected. Creating compressed archive... INFO: Log files have been collected and placed in /tmp/sosreport-LogCollector-20131111134045.tar.xz. The MD5 for this file is 7ccbdf1175dc00ba79cf46ddfee336d8 and its size is 5.8M
This bug is currently attached to errata RHBA-2013:15255. 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-0039.html