Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1620271

Summary: enable rhv_analyzer plugin for sos >= 3.6
Product: Red Hat Enterprise Virtualization Manager Reporter: Douglas Schilling Landgraf <dougsland>
Component: ovirt-log-collectorAssignee: Douglas Schilling Landgraf <dougsland>
Status: CLOSED ERRATA QA Contact: Lukas Svaty <lsvaty>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.2.6CC: danken, dougsland, lleistne, mgoldboi, michal.skrivanek, trichard
Target Milestone: ovirt-4.2.7Keywords: FieldEngineering, ZStream
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: ovirt-log-collector-4.2.7-1.el7ev Doc Type: Enhancement
Doc Text:
The ovirt-log-collector now includes the RHV Log Collector Analyzer report. This analysis is generated by the rhv-log-collector-analyzer tool, which analyzes the RHV environment and detects anomalies in the system.
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-05 15:04:26 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: 1634724    

Description Douglas Schilling Landgraf 2018-08-22 20:43:44 UTC
Description of problem:

In sos 3.6-5 (7.6.z) we will include rhv_analyzer plugin to add support to rhv-log-collector-analyzer.

ovirt-log-collector should add the support to this new plugin.

Comment 1 Dan Kenigsberg 2018-08-23 05:43:46 UTC
Just remember to require the new version of sos report in our spec.

This SHOULD be documennted as it would cause longer time to pull the report.

It is also important to advertise that this lovely analysis is to be found in each tarball.

Comment 2 Sandro Bonazzola 2018-08-23 06:31:47 UTC
(In reply to Dan Kenigsberg from comment #1)
> Just remember to require the new version of sos report in our spec.
> 
> This SHOULD be documennted as it would cause longer time to pull the report.
> 
> It is also important to advertise that this lovely analysis is to be found
> in each tarball.

Tentatively targeted to 4.2.7 but if we need to require sos >= 3.6 we need to wait 4.2.8 at least.

Comment 4 Jiri Belka 2018-10-10 09:16:30 UTC
no meaningful analyzer report

# cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 7.6 Beta (Maipo)


# rpm -q sos ovirt-log-collector; tar xOJf /tmp/sosreport-LogCollector-20181010095924.tar.xz sosreport-LogCollector-20181010095924/sosreport-10-37-138-222-2018-10-10-obboqwc/sos_commands/RhvLogCollectorAnalyzer/analyzer-report.html | elinks -dump
sos-3.6-9.el7.noarch
ovirt-log-collector-4.2.7-1.el7ev.noarch
   Table of Contents
   Last updated 2018-10-10 09:58:42 CEST

although json output has some date

# tar xOJf /tmp/sosreport-LogCollector-20181010095924.tar.xz sosreport-LogCollector-20181010095924/sosreport-10-37-138-222-2018-10-10-obboqwc/sos_commands/RhvLogCollectorAnalyzer/rhv-log-collector-analyzer_--json | head
{
    "hostname": "localhost", 
    "rhv-log-collector-analyzer": [
        {
            "bugzilla": "", 
            "description": "All Datacenter(s) available", 
            "file": "datacenter_show_all.sql", 
            "hash": "9ee69004e63d8a0ebd0b61c977c33d74", 
            "id": "2b2564fec3106730f3e269b53e3bcbb1648c4b863ec3f194373d098b0ab40917", 
            "id_host": "d0745d58abb3418485228c47c23854de", 
...

Comment 10 Douglas Schilling Landgraf 2018-10-16 17:30:54 UTC
Hi Jiri,

(In reply to Jiri Belka from comment #4)
> no meaningful analyzer report
> 
> # cat /etc/redhat-release 
> Red Hat Enterprise Linux Server release 7.6 Beta (Maipo)
> 
> 
> # rpm -q sos ovirt-log-collector; tar xOJf
> /tmp/sosreport-LogCollector-20181010095924.tar.xz
> sosreport-LogCollector-20181010095924/sosreport-10-37-138-222-2018-10-10-
> obboqwc/sos_commands/RhvLogCollectorAnalyzer/analyzer-report.html | elinks
> -dump
> sos-3.6-9.el7.noarch
> ovirt-log-collector-4.2.7-1.el7ev.noarch
>    Table of Contents
>    Last updated 2018-10-10 09:58:42 CEST
> 
> although json output has some date
> 
> # tar xOJf /tmp/sosreport-LogCollector-20181010095924.tar.xz
> sosreport-LogCollector-20181010095924/sosreport-10-37-138-222-2018-10-10-
> obboqwc/sos_commands/RhvLogCollectorAnalyzer/rhv-log-collector-analyzer_--
> json | head
> {
>     "hostname": "localhost", 
>     "rhv-log-collector-analyzer": [
>         {
>             "bugzilla": "", 
>             "description": "All Datacenter(s) available", 
>             "file": "datacenter_show_all.sql", 
>             "hash": "9ee69004e63d8a0ebd0b61c977c33d74", 
>             "id":
> "2b2564fec3106730f3e269b53e3bcbb1648c4b863ec3f194373d098b0ab40917", 
>             "id_host": "d0745d58abb3418485228c47c23854de", 
> ...

Can I have access to RHVM machine that generated the sosreport please?

Comment 11 Douglas Schilling Landgraf 2018-10-18 16:02:29 UTC
I was able to login into the system and identified what happened.

This initial version of --live only check issues in the system and for this RHV deploy (4.2.7), no issues were found. On the other hand, --live --json also display the INFO data like number of clusters, datacenters, etc so we can provide to other systems like Insights all information.

For 4.2.8 we can improve this and have both options displaying the same data.

Comment 14 Lucie Leistnerova 2018-10-24 09:16:47 UTC
sos/plugins/rhv_analyzer.py exists and ovirt-log-collector result contains RhvLogCollectorAnalyzer with rhv-log-collector-analyzer output

verified in 
ovirt-log-collector-4.2.7-1.el7ev.noarch
sos-3.6-9.el7.noarch

And also analyzer-report.html and rhv-log-collector-analyzer_--json seems to have the same data now. So I don't see any other issue here. Feel free to open new BZ when the data from the analyzer are not correct.

Comment 17 errata-xmlrpc 2018-11-05 15:04:26 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://access.redhat.com/errata/RHEA-2018:3488