Bug 1894011
| Summary: | build failure: centos repo cannot be reached from brew | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Joep van Delft <jdelft> |
| Component: | Networking | Assignee: | Andrew McDermott <amcdermo> |
| Networking sub component: | router | QA Contact: | Hongan Li <hongli> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | urgent | ||
| Priority: | urgent | CC: | aos-bugs, misalunk |
| Version: | 3.11.0 | ||
| Target Milestone: | --- | ||
| Target Release: | 3.11.z | ||
| 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: | 2020-11-18 14:09:53 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Joep van Delft
2020-11-03 10:22:41 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? 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. 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 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 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 |