Bug 1808257

Summary:	Error when Image-stream tag from internal registry option is selected
Product:	OpenShift Container Platform	Reporter:	divgupta
Component:	Dev Console	Assignee:	divgupta
Status:	CLOSED ERRATA	QA Contact:	Jaivardhan Kumar <jakumar>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.4	CC:	aos-bugs, jakumar, nmukherj, rgarg
Target Milestone:	---
Target Release:	4.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:	1802570	Environment:
Last Closed:	2020-05-04 11:43:15 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1802570
Bug Blocks:

Description divgupta 2020-02-28 06:28:00 UTC

+++ This bug was initially created as a clone of Bug #1802570 +++

Description of problem:

There are 2 scenarios in which this error occurs:

1) When Image stream tag is selected from the internal registry in deploy image add flow, UI crashes `Invariant Violation`.

Steps to reproduce:

1. Navigate to Deploy Image add option
2. First select Image name from external registry and search for this image 
   'yapei/wordpress`
3. Then select Image stream tag from internal registry option.
4. UI crashes with `Invariant Violation` error.

2) In internal registry deploy image edit flow, initially if imagestream is changed after changing the namespace, `SearchStatus` component crashes UI giving `Invariant Violation` error.

Steps to reproduce:
Please see the attached gif.

Comment 3 Jaivardhan Kumar 2020-03-03 15:16:32 UTC

Verified on 

OpenShift Version
4.4.0-0.ci-2020-03-03-033811
Kubernetes Version
v1.17.1
Channel
stable-4.4
Cluster ID
37161db2-0014-4306-b745-440768152cb5
API Server
https://api.sp79.devcluster.openshift.com:6443

Comment 5 errata-xmlrpc 2020-05-04 11:43:15 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:0581