Bug 1658898
Summary: | Imagestreams and templates can't be recreate/update under Managed status | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | XiuJuan Wang <xiuwang> |
Component: | ImageStreams | Assignee: | Gabe Montero <gmontero> |
Status: | CLOSED ERRATA | QA Contact: | XiuJuan Wang <xiuwang> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.1.0 | CC: | aos-bugs, jokerman, mmccomas, wewang, wzheng, xiuwang |
Target Milestone: | --- | Keywords: | Regression |
Target Release: | 4.1.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | No Doc Update | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-06-04 10:41:14 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
XiuJuan Wang
2018-12-13 06:34:20 UTC
Hmm ... conflict churn. The "retry imagestream mysql because in progress is not yet true and retryCount is not exceeded" messages on the imagestreams you did not change @XiuJuan could indicate a problem with setting to true in the first place. I'll try to recreate, but if you can supply the entire pod log instead of the snippet you posted, that could help just in case this is a timing issue. This kind error "error syncing key (openshift/jenkins): retry imagestream jenkins because in progress is not yet true and retryCount is not exceeded" always exist, no matter the imagestream if modified. http://pastebin.test.redhat.com/683878 After delete/retag imagestreams for 1 hour, the imagestreams don't be recreate/update. Could reproduce this issue with latest origin image. docker.io/openshift/origin-cluster-samples-operator latest 55cb422f7826 2 hours ago 281 MB OK the complete log was helpful. I see where the bug is now. Starting on a fix. Also, the recovery of the jenkins imagestream after you tag in an invalid registry is not something the operator does @XiuJuan. Ben and I have discussed such a notion, and the decision is that it is not "meets min" for 4.0. If the admin corrupts the imagestream in such a way, he can delete the sampleresource or mark it Removed to recover. But the deleted dotnet imagestream from your description should be recovered. PR has merged Tested delete dotnet, can be recreated, and jenkins can be retag, tested in next_gen_installer env v0.7.0-master-4-ga4e426ee762c20019bbb90fe35d33c9b26d23393 and latest origin image docker.io/openshift/origin-cluster-samples-operator eb7db30d28bc 27 hours ago 281 MB $ oc delete is dotnet -n openshift imagestream.image.openshift.io "dotnet" deleted $ oc get is dotnet -n openshift NAME IMAGE REPOSITORY TAGS UPDATED dotnet image-registry.openshift-image-registry.svc:5000/openshift/dotnet 2.0,2.1,latest 6 seconds ago $ oc get is jenkins -n openshift NAME IMAGE REPOSITORY TAGS UPDATED jenkins image-registry.openshift-image-registry.svc:5000/openshift/jenkins test,1,2,latest 11 seconds ago This is a 4.0 specific bug fixed in 4.0 dev cycle ... no doc update needed 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-2019:0758 |