Description of problem: Should always populate tags of new image for imagestream Version-Release number of selected component (if applicable): OCP 3.7.7 Cockpit 155 How reproducible: Always Steps to Reproduce: 1.Create ImageStream, set it to "Sync all tags from a remote image repository" and Pull from "docker.io/openshift/hello-openshift" 2.Edit ImageStream, set Pull from "docker.io/yapei/busybox" Actual results: 2.Still show Tags for old image "docker.io/openshift/hello-openshift" Expected results: 2. After imagestream pulling repository changed, should pull new images and sync its tags Additional info:
Work around would be use the cli. # oc import-image NAME --all --confirm I was able to reproduce as well with the registry console as well.
https://github.com/cockpit-project/cockpit/issues/4081
We found this issue recently because we missed the checkpoint in test case, and I think it's not a release blocker for registry console
Peter fixed this at least partially in https://github.com/cockpit-project/cockpit/pull/8308 . @Peter: What aspect is left?
The pulling part is fixed. But the removing tags part doesn't work well. Needs to fixed along with #1373332.
The bug still exists on OCP v3.7.26.
bugzilla keeps complaining about "missing doc text"; this is a small bug fix (and there isn't even a fix yet), so disabling the doc update for now.
As said above, tag syncing on pulling should work in the current release. The cleanup on removing tags depends on 1373332 which needs an API in OpenShift. Thus this part is blocked and definitively won't be fixed in 3.7.z, so moving milestone.
(In reply to Martin Pitt from comment #14) > As said above, tag syncing on pulling should work in the current release. > The cleanup on removing tags depends on 1373332 which needs an API in > OpenShift. Thus this part is blocked and definitively won't be fixed in > 3.7.z, so moving milestone. When you say current release, what release version exactly are you implying to? The current release is v3.7.23. I believe the bug still exists there.
@Taneem: The pull fix landed in Cockpit 159 on Jan 10, and got built for RHEL on the same day (https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=638219). I don't have insights into which cockpit version went into which RHEL Container Platform release, though - I understand releasing involves grabbing a current Cockpit brew build and including that?
Hi Martin, If I'm understanding correctly, what needs to happen is for OpenShift's build to ensure it's pulling in the latest GA version of cockpit. It looks like 160 was release recently. I'm make sure the OpenShift build team knows.
To be clear, is any fix required in the OpenShift codebase or is this limited to cockpit?
@Brenton: For that part of the fix it's only Cockpit (≥ 159). I see you are pulling in 160, that seems fine.
Hi Martin, I apologize if I wasn't clear. Does any OpenShift code need to be fixed to resolve this bug? When you say, "that part of the fix" it makes me think there is another part that I'm not understanding.
Ah, sorry; the "other part" refers to bug 1373332, but I think it's fine to restrict the scope of *this* bug to the already fixed part, and keep 1373332 for the other one (that needs OpenShift fixes, or at least documentation how to do it with the API).
> it's fine to restrict the scope of *this* bug to the already fixed part ... which is a fix only in Cockpit, no OpenShift change necessary.
Since bug is targeted to 3.11 and issue still reproduce on latest v3.7.42, I think it should be dropped from errata 32336, right?
Move back to MODIFIED
Sorry should be ASSIGNED
> I think it should be dropped from errata 32336 Right, and this happened. Clearing needinfo request.
Minor feature/bug, not relevant any more for current OpenShift, and this product is in low-maintenance mode.