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

Bug 1653202

Summary: Build ovirt-lldp-labeler for RHV 4.2.8 RHEL7
Product: Red Hat Enterprise Virtualization Manager Reporter: Ales Musil <amusil>
Component: ovirt-lldp-labelerAssignee: Ales Musil <amusil>
Status: CLOSED ERRATA QA Contact: Michael Burman <mburman>
Severity: low Docs Contact:
Priority: medium    
Version: 4.2.8CC: amusil, danken, ratamir, Rhev-m-bugs
Target Milestone: ovirt-4.2.8Keywords: Rebase, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-01-22 12:44:39 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ales Musil 2018-11-26 08:53:02 UTC
Build ovirt-lldp-labeler for RHV 4.2.8 RHEL7

Comment 8 Dan Kenigsberg 2018-12-13 20:22:34 UTC
The proud owner of this bug is Ales, though I suspect Anton should be called in.

Comment 12 Dan Kenigsberg 2018-12-17 07:12:03 UTC
Ok, so it *is* included in the latest build, but it is not installed by default.

If we want to pull it in by default, we can simply Requires it in engine.spec. But I believe that currently it is enough to make it available for a customer that wants to `yum install ovirt-lldp-labeler`. We do not enable it by default, so we may (temporarily?) also require installing it first.

Comment 14 Dan Kenigsberg 2018-12-17 07:19:46 UTC
shipping = placing an RPM in a channel, where a customer can `yum install` it.
        != installing by default.

I agree that the latter would be better. But if the first is working, I'd verify this bug.

Comment 16 Michael Burman 2018-12-17 07:24:17 UTC
Verified on - rhvm-4.2.8.1-0.1.el7ev.noarch

Comment 18 errata-xmlrpc 2019-01-22 12:44:39 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-2019:0119