Bug 1787492

Summary: error message is not clear when user tries to search and deploy from private image
Product: OpenShift Container Platform Reporter: Yadan Pei <yapei>
Component: Dev ConsoleAssignee: Karthik Jeeyar <kjeeyar>
Status: CLOSED ERRATA QA Contact: Ruchir Garg <rgarg>
Severity: low Docs Contact:
Priority: medium    
Version: 4.3.0CC: aos-bugs, kjeeyar, nmukherj, viraj
Target Milestone: ---   
Target Release: 4.4.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Enhancement
Doc Text:
Feature: Improve the error message on the internal registry feature Reason: If there is any server side error, then it has to be properly notified to the user to help them understand the problem better. Result: Helps the user to identify the problem happened during the submission of the request.
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-05-04 11:22:00 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:

Description Yadan Pei 2020-01-03 05:43:14 UTC
Description of problem:
When user tries to search private image and deploy app from it, the first time we click search button gives unclear error message 

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

How reproducible:

Steps to Reproduce:
1. Switch to Developer Console -> +Add -> Container Image -> yapei/wordpress, click on Search button
2. Click Search button again

Actual results:
1. It shows this error message on the first search
 Could not load image metadata. 
2. On the second search, it shows 
Could not load image metadata.

you may not have access to the container image "docker.io/yapei/wordpress:latest"

Expected results:
1. It should show 'you may not have access to the container image "docker.io/yapei/wordpress:latest' even at the first search, the first message seems useless

Additional info:

Comment 1 cvogt 2020-01-06 16:51:19 UTC
Jira tracker: https://issues.redhat.com/browse/ODC-2677

Comment 3 Vikram Raj 2020-02-06 10:24:58 UTC
This bug has been fixed I validated it on

Cluster: 4.4.0-0.ci-2020-02-05-054333
Brower: Firefox(71.0), Chrome (79.0.3945.79)
User: Admin and consoledeveloper

Comment 5 errata-xmlrpc 2020-05-04 11:22:00 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.