Bug 1936854 - Incorrect imagestream is shown as selected in knative service container image edit flow
Summary: Incorrect imagestream is shown as selected in knative service container image...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.6
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.8.0
Assignee: divgupta
QA Contact: Gajanan More
Depends On:
Blocks: 1937356
TreeView+ depends on / blocked
Reported: 2021-03-09 11:07 UTC by divgupta
Modified: 2021-07-27 22:52 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-07-27 22:51:56 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift console pull 8338 0 None open Bug 1936854:Fix to show correct internal image-stream name in container image edit flow's internal registry image-stream... 2021-03-09 11:07:44 UTC
Red Hat Product Errata RHSA-2021:2438 0 None None None 2021-07-27 22:52:20 UTC

Description divgupta 2021-03-09 11:07:05 UTC
Description of problem:
When support for selecting the runtime icon from the runtime icon dropdown was added to the edit flows the previous code for showing runtime icon for deployments created on creating an app using container image flow internal registry option was not properly cleaned up for knative service resource. Label 'app.kubernetes.io/name' which is used for getting the internal imagestream name is set incorrectly with runtime icon name instead of the imagestream name for knative service resource.

How reproducible: Always

Steps to Reproduce:
1.Create an app using container image internal registry option and resource as Knative Service.
2.Click on edit <app-name> action from node context menu.

Actual results:
Notice that in imagestream dropdown under internal registry option runtime icon name is shown instead of the previously selected imagestream.

Expected results:
Correct imagestream should be selected.

Additional info:

Comment 1 Christoph Jerolimov 2021-03-23 10:29:11 UTC
Verified on 4.8.0-0.nightly-2021-03-22-064955

Comment 2 Christoph Jerolimov 2021-03-23 10:37:53 UTC
Trigger Jira update

Comment 5 errata-xmlrpc 2021-07-27 22:51:56 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 (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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