Bug 1507784 - [atomic registry] Repository column shows unknown for any images
Summary: [atomic registry] Repository column shows unknown for any images
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Registry Console
Version: 3.7.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: 3.9.z
Assignee: Martin Pitt
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-31 07:27 UTC by Xingxing Xia
Modified: 2019-11-20 19:07 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-20 19:07:29 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
repository column (42.30 KB, image/png)
2017-10-31 07:27 UTC, Xingxing Xia
no flags Details
3.7 openshift console images page column.png (46.03 KB, image/png)
2017-11-14 03:23 UTC, Xingxing Xia
no flags Details

Description Xingxing Xia 2017-10-31 07:27:56 UTC
Created attachment 1345776 [details]
repository column

Description of problem:
In registry console "Images" page, "Repository" column shows "unknown" for any images

Version-Release number of selected component (if applicable):
openshift v3.7.0-0.184.0
registry.reg-aws.../openshift3/registry-console:v3.7 (cockpit version 151)

How reproducible:
Always

Steps to Reproduce:
1. In registry console, create project
2. Create image stream by setting "Pull from" openshift/hello-openshift
3. In "Images" page, check "Repository" column for the image stream
4. Create empty image stream, push image to it by `docker tag/push ...`, check step 3 for the pushed image

Actual results:
3 and 4: "Repository" column shows "unknown", no matter the image is made via pulled or pushed, see attachment

Expected results:
3 and 4: "Repository" column should show proper value

Additional info:

Comment 1 Peter 2017-10-31 13:20:16 UTC

*** This bug has been marked as a duplicate of bug 1507460 ***

Comment 2 Xingxing Xia 2017-11-13 07:56:06 UTC
At the time closing this, it was thought this bug and the other bug are irrelevant (see next paragraph), the closing deserves check again after the other bug is verified.
Now bug 1507460 is verified in cockpit 155, but check again this bug, this bug still happens. Reopening and the severity could be lower

Comment 3 Peter 2017-11-13 15:34:05 UTC
Are you seeing the same behavior in the openshift webconsole?

Comment 4 Peter 2017-11-13 15:37:13 UTC
Looks like the field we and the openshift console were using has been depreciated.

https://github.com/openshift/origin/pull/16181/commits/856dfa1793c4aee02cdd33ca08c52728cfdca09c

Guess we need to re-figure the design as there is no 1-1 replacement.

Comment 5 Xingxing Xia 2017-11-14 03:23:42 UTC
Created attachment 1351784 [details]
3.7 openshift console images page column.png

As of latest v3.7, openshift console has a corresponding column "Docker Repo", see attachment
Maybe need re-figure when depreciated in future

Comment 6 Peter 2017-11-14 03:38:31 UTC
You are right, this isn't depreciated yet.

Fixing upstream here: https://github.com/cockpit-project/registry-image-widgets/pull/13

Comment 8 Xingxing Xia 2018-01-25 10:29:56 UTC
Checked in latest 3.9 env with reg-aws openshift3/registry-console:v3.9.0-0.23.0 (image id ca8fc61eb1fa, cockpit 155), "Repository" column still shows "unknown". Seems the fix does not come in latest registry-console image?

Comment 11 Stephen Cuppett 2019-11-20 19:07:29 UTC
OCP 3.6-3.10 is no longer on full support [1]. Marking CLOSED DEFERRED. If you have a customer case with a support exception or have reproduced on 3.11+, please reopen and include those details. When reopening, please set the Target Release to the appropriate version where needed.

[1]: https://access.redhat.com/support/policy/updates/openshift


Note You need to log in before you can comment on or make changes to this bug.