Bug 1760767 - Image name is not properly shown in web console
Summary: Image name is not properly shown in web console
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 3.11.z
Assignee: Robb Hamilton
QA Contact: Yadan Pei
URL:
Whiteboard:
: 1776830 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-10-11 09:56 UTC by Sergio G.
Modified: 2024-04-14 04:25 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: In order to optimize the display of image names for deployment configs, there is some clever code that formats the display of image names. Consequence: In the case outlined in this bug, the image name can end up formatted in a confusing and incorrect way. Fix: Remove the special formatting around the display of image names if the image is not part of a deployment config. Result: The image name displays correctly.
Clone Of:
Environment:
Last Closed: 2020-03-20 00:12:40 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Detail of the difference in the image names. Took when accessing to the overview page. (19.90 KB, image/png)
2019-10-11 09:59 UTC, Sergio G.
no flags Details
DC image display on overview (72.83 KB, image/png)
2020-03-09 09:07 UTC, XiaochuanWang
no flags Details
image name of Deployment display well (86.54 KB, image/png)
2020-03-09 09:09 UTC, XiaochuanWang
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:0793 0 None None None 2020-03-20 00:12:54 UTC

Description Sergio G. 2019-10-11 09:56:20 UTC
Description of problem:
When accessing to the web console the image name is not properly shown. 

In example, the image is "docker.io/fedora/tools:latest" but only "fedora/tools" is shown.

In the other hand, if the image is "docker.io/fedora:latest", the full name is shown.


Version-Release number of selected component (if applicable):
Reproduced in 3.11.135


How reproducible:
Always


Steps to Reproduce:
1. Deploy two different pods:
 $ oc run sleep1 --image=docker.io/fedora/tools:latest --command -- sleep 3600
 $ oc run sleep2 --image=docker.io/fedora:latest --command -- sleep 3600

2. Access to the web console and check the overview of the project and/or the pod details


Actual results:
See screenshots


Expected results:
Visualize the whole image information and not just a part of it


Additional info:
 - https://bugzilla.redhat.com/show_bug.cgi?id=1722815 does not apply (this issue reproduces in 3.11.135) but it's likely related

Comment 1 Sergio G. 2019-10-11 09:59:28 UTC
Created attachment 1624665 [details]
Detail of the difference in the image names. Took when accessing to the overview page.

Comment 2 Sergio G. 2019-10-18 08:50:00 UTC
Any feedback about the issue? Is this the expected behavior when visualizing images or is it actually a bug?

Comment 3 Samuel Padgett 2019-12-02 14:08:10 UTC
*** Bug 1776830 has been marked as a duplicate of this bug. ***

Comment 5 bpeterse 2020-01-30 18:42:37 UTC
This is the functionality in the old console (inferring from your screenshot) at the time of 3.11.  The new console displays `docker.io/fedora/tools:latest` or `docker.io/fedora:latest` in the containers table of deployments, pods, etc. and is probably the console you want to be using.

Comment 6 Sergio G. 2020-01-30 20:05:54 UTC
I can understand that the new console in OpenShift 4.x doesn't reproduces the bad behavior, but 3.11 (which is the one that the customers are using) reproduces the bad behavior so this is a real bug. 

If you want to close the case even when there's a real bug, it's okay, but then it's a WONTFIX. Discussing a WONTFIX with a customer using a supported version (3.11 is fully supported until June 2020) will be difficult but if this is firm, please confirm and I will update the support case according to your decision.

Comment 7 bpeterse 2020-02-06 15:40:16 UTC
Fortunately 3.11 supports both consoles, there is a selector in the toolbar to switch to the new Management Console.  Its the preferred direction for customers as it is the only console in 4.x.

Comment 8 Sergio G. 2020-02-06 20:09:51 UTC
Ok, so we have a bug in the console and we are not fixing it because there's another console which is not the default and which doesn't have all the functionality that the main one but on it the bug doesn't reproduces.

If that's the answer, I am okay with it, but I can't agree with it. You can close the bug, but please be coherent and set it as WONTFIX and not NOTABUG.

Thanks,
Sergio

Comment 9 Robb Hamilton 2020-02-06 20:22:12 UTC
Sergio, I think we've found a simple, low risk fix for the bug.  See https://github.com/openshift/origin-web-console/pull/3166.

Comment 10 Sergio G. 2020-02-06 20:35:35 UTC
@Rob that's awesome, good news.

Comment 17 XiaochuanWang 2020-03-09 09:07:33 UTC
Created attachment 1668611 [details]
DC image display on overview

Comment 18 XiaochuanWang 2020-03-09 09:09:54 UTC
Created attachment 1668612 [details]
image name of Deployment display well

Comment 19 XiaochuanWang 2020-03-09 09:11:04 UTC
This is fixed as the PR https://github.com/openshift/origin-web-console/pull/3166 does.
Please refer to the screenshots.

Verified on the version:
OpenShift Master: v3.11.187
Kubernetes Master: v1.11.0+d4cacc0
OpenShift Web Console: 3.11.187-1-8065549

Comment 20 Yadan Pei 2020-03-12 02:58:58 UTC
Bug has been verified so clear the needinfo

Comment 22 errata-xmlrpc 2020-03-20 00:12:40 UTC
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:0793

Comment 23 Red Hat Bugzilla 2024-04-14 04:25:20 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days


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