Bug 1378732

Summary: [atomic registry] Invalid repo for sync istags will not prompt any warning or errors info, even failed to import when repo is updated
Product: OpenShift Container Platform Reporter: XiaochuanWang <xiaocwan>
Component: RFEAssignee: Michal Minar <miminar>
Status: CLOSED WONTFIX QA Contact: Xiaoli Tian <xtian>
Severity: low Docs Contact:
Priority: low    
Version: 3.3.0CC: aos-bugs, dperpeet, jokerman, mfojtik, mmccomas, pweil
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-06-12 11:56:23 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 XiaochuanWang 2016-09-23 08:39:42 UTC 
Description of problem:
Create an IS which sync all istag from remote repo, save a invalid repo. There is no warning/error info anywhere. 
When repo is updated to a valid one, IS failed to import.

Version-Release number of selected component (if applicable):
openshift3/registry-console:3.3

How reproducible:
Always

Steps to Reproduce:
1. Create an IS in a project with invalid repo by:
1) from Images, select a project, hit "New Image Stream"
2) select "Sync all tags ..." for "Populate", input a invalid repo in "Pull from", eg. "abcd"
2. Check Images page.
3. Update the istag with valid repo:
1) From Images select the created image
2) Click the update icon in the top-right corner. 
3) Update the repo to a valid repo, eg. docker.io/openshift/hello-openshift. Keep the Populate still "sync all tags from a remote image repository", then hit Change button.

Actual results:
1. There is no warning or error info when create an IS with invalid repo. IS created successfully. 
2. There is no warning or error info anywhere.
3. IS updated successfully but the image is failed to import without any message even wait for about 10 mins (not sure if it's a bug)

Expected results:
1. There is a warning about the invalid repo on "Pull from" value and the "Create" button should be disabled
2. If the imagestream created, at least there should be a message that the repo is invalid
3. Image should be imported with the valid repo.

Additional info:
Comment 2 Peter 2017-05-05 23:35:02 UTC 
The core of this issue is that we need to be able to show errors when importing fails.

As far as I can tell this is a limitation of the current rest API. When importing a repository into an image stream there is no way to get a ImageStreamImportStatus for an existing image stream.

If i'm wrong about that, please assign back to me.
Comment 4 Maciej Szulik 2017-06-02 13:05:21 UTC 
I've created https://trello.com/c/5Uq7C9Se/956-provide-reasonable-status-data-from-image-streams since there's a bit more we need to do to improve Image Stream statuses.
Comment 6 Kirsten Newcomer 2019-06-12 11:56:23 UTC 
With the introduction of OpenShift 4, Red Hat has delivered or roadmapped a substantial number of features based on feedback by our customers.  Many of the enhancements encompass specific RFEs which have been requested, or deliver a comparable solution to a customer problem, rendering an RFE redundant.

This bz (RFE) has been identified as a feature request not yet planned or scheduled for an OpenShift release and is being closed. 

If this feature is still an active request that needs to be tracked, Red Hat Support can assist in filing a request in the new JIRA RFE system, as well as provide you with updates as the RFE progress within our planning processes. Please open a new support case: https://access.redhat.com/support/cases/#/case/new 

Opening a New Support Case: https://access.redhat.com/support/cases/#/case/new 

As the new Jira RFE system is not yet public, Red Hat Support can help answer your questions about your RFEs via the same support case system.