Bug 1901982
| Summary: | [sig-builds][Feature:Builds] build can reference a cluster service with a build being created from new-build should be able to run a build that references a cluster service | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Joel Speed <jspeed> | |
| Component: | Build | Assignee: | Gabe Montero <gmontero> | |
| Status: | CLOSED ERRATA | QA Contact: | XiuJuan Wang <xiuwang> | |
| Severity: | urgent | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 4.7 | CC: | aos-bugs, gmontero, lsm5, obulatov, umohnani | |
| Target Milestone: | --- | |||
| Target Release: | 4.7.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | No Doc Update | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1902221 (view as bug list) | Environment: |
[sig-builds][Feature:Builds] build can reference a cluster service with a build being created from new-build should be able to run a build that references a cluster service
[sig-builds][Feature:Builds] prune builds based on settings in the buildconfig should prune completed builds based on the successfulBuildsHistoryLimit setting
[sig-auth][Feature:SecurityContextConstraints] TestPodDefaultCapabilities
[sig-builds][Feature:Builds] Optimized image builds should succeed
|
|
| Last Closed: | 2021-02-24 15:35:50 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: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1895107, 1902029, 1902215, 1902221 | |||
|
Description
Joel Speed
2020-11-26 14:25:52 UTC
Also seeing a significant number of failures for "[sig-builds][Feature:Builds] prune builds based on settings in the buildconfig should prune completed builds based on the successfulBuildsHistoryLimit setting" reporting docker hub rate limiting issues as well https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ocp-4.7-e2e-vsphere/1331455308672798720 Also seeing a significant number of failures for "[sig-auth][Feature:SecurityContextConstraints] TestPodDefaultCapabilities" reporting docker hub rate limiting issues as well https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ocp-4.7-e2e-vsphere/1331447713761333248 *** Bug 1901192 has been marked as a duplicate of this bug. *** *** Bug 1901734 has been marked as a duplicate of this bug. *** *** Bug 1902205 has been marked as a duplicate of this bug. *** OK, Clayton wants to solve the docker.io throttling with Bug 1816812 and https://github.com/openshift/origin/pull/24887 Now, that change involves more than just switching from docker.io, and has been in flight for a few weeks now. Clayton thinks he is close to having this go green, so we are holding tight for now, but are in communication with him and monitoring. If need be we have a more limited, back up option, borrowing from his changes, to address docker.io usage in the build e2e's if need be. Clayton's https://github.com/openshift/origin/pull/24887 has been tagged for merge. Once it does, I'll a quick sanity check of sig-build e2e's in openshift/origin and assuming we look good re: docker.io I'll mark this bug a dup of https://bugzilla.redhat.com/show_bug.cgi?id=1816812 Clayton's PR has merged. The BZ is on QA. That said, I noticed a couple of busybox stragglers still in the build e2e's after Clayton's PR merged. I'm using this bug to deal with those. I have a PR up passing e2e's. Will associated this with that momentarily. *** Bug 1904682 has been marked as a duplicate of this bug. *** 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. https://access.redhat.com/errata/RHSA-2020:5633 |