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

Bug 1608013

Summary: Require rhv-log-collector-analyzer
Product: Red Hat Enterprise Virtualization Manager Reporter: Douglas Schilling Landgraf <dougsland>
Component: ovirt-engineAssignee: Douglas Schilling Landgraf <dougsland>
Status: CLOSED ERRATA QA Contact: Pavol Brilla <pbrilla>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.2.6CC: danken, lsurette, lsvaty, Rhev-m-bugs, sbonazzo, srevivo, tburke, ylavi
Target Milestone: ovirt-4.2.6Keywords: FieldEngineering, ZStream
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-09-04 13:41:42 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:

Description Douglas Schilling Landgraf 2018-07-24 18:24:32 UTC
Description of problem:

Since 4.2.5 we ship rhv-log-collector-analyzer rpm, we should require the package
into the ovirt-engine spec.

Comment 2 RHV bug bot 2018-08-28 18:32:48 UTC
WARN: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason:

[Found non-acked flags: '{'rhevm-4.2.z': '?'}', ]

For more info please contact: rhv-devops: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason:

[Found non-acked flags: '{'rhevm-4.2.z': '?'}', ]

For more info please contact: rhv-devops

Comment 3 Pavol Brilla 2018-08-31 08:35:03 UTC
# yum deplist rhvm | grep rhv-log-collector-analyzer
  dependency: rhv-log-collector-analyzer
   provider: rhv-log-collector-analyzer.noarch 0.1.5-0.el7ev
# yum list ovirt-engine
Installed Packages
ovirt-engine.noarch          4.2.6.4-0.1.el7ev         @rhv-4.2.6

Comment 5 errata-xmlrpc 2018-09-04 13:41:42 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/RHBA-2018:2623