Bug 1760767
| Summary: | Image name is not properly shown in web console | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Sergio G. <sgarciam> | ||||||||
| Component: | Management Console | Assignee: | Robb Hamilton <rhamilto> | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 3.11.0 | CC: | aos-bugs, bpeterse, jokerman, mdhanve, spadgett, travi, xiaocwan, xtian, yapei | ||||||||
| Target Milestone: | --- | Keywords: | Reopened | ||||||||
| Target Release: | 3.11.z | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| 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.
|
Story Points: | --- | ||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2020-03-20 00:12:40 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: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Sergio G.
2019-10-11 09:56:20 UTC
Created attachment 1624665 [details]
Detail of the difference in the image names. Took when accessing to the overview page.
Any feedback about the issue? Is this the expected behavior when visualizing images or is it actually a bug? *** Bug 1776830 has been marked as a duplicate of this bug. *** 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. 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. 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. 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 Sergio, I think we've found a simple, low risk fix for the bug. See https://github.com/openshift/origin-web-console/pull/3166. @Rob that's awesome, good news. Created attachment 1668611 [details]
DC image display on overview
Created attachment 1668612 [details]
image name of Deployment display well
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 Bug has been verified so clear the needinfo 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 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days |