Bug 1290058

Summary:	[RFE] auto-create or at least hint that dedicated registry needs to be created for ISV registries
Product:	Red Hat Satellite	Reporter:	Dirk Herrmann <dherrman>
Component:	Container Management	Assignee:	Daniel Lobato Garcia <dlobatog>
Status:	CLOSED WONTFIX	QA Contact:	Katello QA List <katello-qa-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	Unspecified	CC:	bkearney, tomckay
Target Milestone:	Unspecified	Keywords:	FutureFeature, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-05-22 13:23:52 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:

Description Dirk Herrmann 2015-12-09 15:14:16 UTC

Description of problem:

Our Red Hat federated index (registry.access.redhat.com) shows docker search results from our ISV registries pointing to these dedicated registries (for example registry-mariadbcorp.rhcloud.com). 

If our Red Hat registry has been configured as an external registry in Satellite 6 the federated index shows results from our ISV registries but if a user selects them it causes a 404 error since the registry the images lives in is not the same as configured and used. 

Instead of the 404 error message we should show a hint that these ISV registries need to be configured as additional external registries including a link to the "New External Registry" page. Automatically creating the selected ISV repo as an external registry would be even better.

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

6.1.4

How reproducible:


Steps to Reproduce:
1. Create Red Hat registry as an external registry 
2. Use the New Container wizard and select the Red Hat registry
3. Search for mariadb and select the registry-mariadbcorp.rhcloud.com/rhel7/mariadb-enterprise-server repo

Actual results:

Error message: 404 Resource not found

Expected results:

Warning: The repository location is outside of the current registry. You need to configure it as an additional external registry first. Go here (Link) to configure this registry.

Additional info:

Comment 1 Bryan Kearney 2016-07-26 19:08:58 UTC

Moving 6.2 bugs out to sat-backlog.

Comment 2 Tom McKay 2017-01-26 13:40:28 UTC

Created redmine issue http://projects.theforeman.org/issues/18251 from this bug