Bug 1898268 - [OVN]: `make check` broken on 4.6
Summary: [OVN]: `make check` broken on 4.6
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.6
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.7.0
Assignee: Alexander Constantinescu
QA Contact: Anurag saxena
Depends On:
Blocks: 1898269 1912388
TreeView+ depends on / blocked
Reported: 2020-11-16 17:42 UTC by Alexander Constantinescu
Modified: 2021-02-24 15:34 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1898269 (view as bug list)
Last Closed: 2021-02-24 15:33:36 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:5633 0 None None None 2021-02-24 15:34:06 UTC

Description Alexander Constantinescu 2020-11-16 17:42:16 UTC
Description of problem:

When running `make check` on release-4.6 of openshift/ovn-kubernetes, the build fails. I suspect this is because https://github.com/openshift/ovn-kubernetes/commit/15661c9d1d23fe0b30d266bda3668ee848884fb5

Version-Release number of selected component (if applicable):

release-4.6 latest

How reproducible:

Steps to Reproduce:
1. Checkout openshift/ovn-kubernetes
2. cd go-controller && make check

Actual results:

Build fails

Expected results:

Build should be successful 
Additional info:

Comment 1 Alexander Constantinescu 2020-11-16 17:44:47 UTC
This does not affect the product, but only the builds of the repository itself. I am thus moving the bug to VERIFIED as I need this bug to get the fix into 4.6, but it does not happen on master.

Comment 4 errata-xmlrpc 2021-02-24 15:33:36 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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.