Bug 1761372
| Summary: | [build-cop] openshift/cli image stream is invalid | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Michal Fojtik <mfojtik> |
| Component: | Samples | Assignee: | Gabe Montero <gmontero> |
| Status: | CLOSED ERRATA | QA Contact: | XiuJuan Wang <xiuwang> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.3.0 | CC: | aos-bugs, bparees, gmontero, jokerman, mfojtik |
| Target Milestone: | --- | ||
| Target Release: | 4.3.0 | ||
| 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-01-23 11:07:15 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
Michal Fojtik
2019-10-14 09:37:50 UTC
Further investigation led to: E1014 04:51:56.306779 1 task.go:77] error running apply for imagestream "openshift/cli" (230 of 443): ImageStream.image.openshift.io "cli" is invalid: spec.tags[latest].from.name: Invalid value: "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:269be241245bce2798f477f53f5094e0c848270a5f1f3bc9a0affa8d3fe4a54f": only tags can be scheduled for import Gabe, didn't you just lift this validation restriction? Not sure why 4.3 wouldn't have picked it up yet..... Yes PRs https://github.com/openshift/openshift-apiserver/pull/29 and https://github.com/openshift/openshift-apiserver/pull/28 are needed to lift that restriction Per the thread https://coreos.slack.com/archives/CB95J6R4N/p1571076950151600 in #aos-art Justin Pierce has found an issue with the applicable image in the release payload. openshift-apiserver has been rebuilt for 4.3; it's in https://openshift-release.svc.ci.openshift.org/releasestream/4.3.0-0.nightly/release/4.3.0-0.nightly-2019-10-15-020113 Gabe since this was basically your changes that needed to land, assigning to the BZ to you to monitor https://prow.svc.ci.openshift.org/job-history/origin-ci-test/logs/release-openshift-ocp-installer-e2e-aws-4.3 to go back to green (or investigate why it continues to fail and open a new BZ if necessary if there are other issues). We got 3 green/success runs early this AM with https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-aws-4.3/50 https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-aws-4.3/51 https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-aws-4.3/52 No artifacts were gathered (the link at least produced a application is not available error). But QE was able to do basic validation with https://bugzilla.redhat.com/show_bug.cgi?id=1755115 to confirm imagestream is created, imported. Some basic triage of other failures after this issue was resolved: 1) Job 54 got a lease problem on initial build. 2) 53 had one prometheus alert test case fail ... opened https://bugzilla.redhat.com/show_bug.cgi?id=1761882 for triage Marking this one verified 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-2020:0062 |