Bug 1894011 - build failure: centos repo cannot be reached from brew
Summary: build failure: centos repo cannot be reached from brew
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 3.11.z
Assignee: Andrew McDermott
QA Contact: Hongan Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-03 10:22 UTC by Joep van Delft
Modified: 2022-08-04 22:30 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-18 14:09:53 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift origin pull 25663 0 None closed Bug 1894011: images/router: Add ART specific Dockerfile 2021-01-25 13:06:29 UTC
Red Hat Product Errata RHBA-2020:5107 0 None None None 2020-11-18 14:09:57 UTC

Description Joep van Delft 2020-11-03 10:22:41 UTC
Description of problem:
Image fails to build on Brew for since https://github.com/openshift/ose/commit/5566962f2f0c97bb46ca1867ed1d19a3e46cc938

Brew environment cannot reach the centos repository.
Example: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=32729902

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

How reproducible:
Have ART build in the brew environment

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Andrew McDermott 2020-11-03 17:44:26 UTC
The change that introduced:

 https://github.com/openshift/ose/commit/5566962f2f0c97bb46ca1867ed1d19a3e46cc938

was reverted in this PR:

 https://github.com/openshift/origin/pull/25542/commits/9c4e00d3dae737583d17c27339eb47b9ae6d6fe8

which merged earlier today.

I'll leave this ASSIGNED for the moment to ensure the newer change doesn't also break the brew build.

Is mirror.openshift.com accessible during a brew build?

Is there a quick way to trigger a brew build for this component?

Comment 2 Joep van Delft 2020-11-03 19:29:47 UTC
Thanks! The resulting brew build failed, however: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=32792016

ART includes already the current 3.11 haproxy rpm, and the repository for that is enabled in https://github.com/openshift/ocp-build-data/blob/60ac4d7f4063d3e0c76d4e30e851af9da107c0aa/images/openshift-enterprise-haproxy-router.yml#L20

One way of approaching this is to maintain separate Dockerfiles for CI and ART, the latter does not manage repositories itself. See e.g. https://github.com/openshift/ocp-build-data/pull/736.

Comment 3 Miheer Salunke 2020-11-05 16:57:16 UTC
Hi,

Just FYI, I had got this mail 

haproxy-1.8.26-1.el7 successfully tagged into rhaos-3.11-rhel-7-image-build by ocp-build/buildvm.openshift.eng.bos.redhat.com
Inbox

Red Hat Buildsystem <buildsys>
Mon, Nov 2, 6:54 PM (4 days ago)
to me, tsmetana

Package: haproxy
NVR: haproxy-1.8.26-1.el7
User: ocp-build/buildvm.openshift.eng.bos.redhat.com
Status: complete
Tag Operation: tagged
Into Tag: rhaos-3.11-rhel-7-image-build

haproxy-1.8.26-1.el7 successfully tagged into rhaos-3.11-rhel-7-image-build by ocp-build/buildvm.openshift.eng.bos.redhat.com

Thanks and regards,
Miheer

Comment 4 Miheer Salunke 2020-11-13 01:20:06 UTC
Got a new email ->

haproxy-1.8.26-1.el7 successfully tagged into rhaos-3.11-rhel-7 by errata/beehive
Inbox

Red Hat Buildsystem <buildsys>
Thu, Nov 12, 8:11 PM (15 hours ago)
to me, yselkowi, tsmetana

Package: haproxy
NVR: haproxy-1.8.26-1.el7
User: errata/beehive
Status: complete
Tag Operation: tagged
Into Tag: rhaos-3.11-rhel-7

haproxy-1.8.26-1.el7 successfully tagged into rhaos-3.11-rhel-7 by errata/beehive

Comment 7 Hongan Li 2020-11-16 01:41:41 UTC
moving to verified per Comment 4.

Comment 9 errata-xmlrpc 2020-11-18 14:09:53 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 (OpenShift Container Platform 3.11.318 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.

https://access.redhat.com/errata/RHBA-2020:5107


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