Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1290058 - [RFE] auto-create or at least hint that dedicated registry needs to be created for ISV registries
Summary: [RFE] auto-create or at least hint that dedicated registry needs to be create...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Container Management
Version: Unspecified
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: Daniel Lobato Garcia
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-09 15:14 UTC by Dirk Herrmann
Modified: 2018-05-22 13:23 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-22 13:23:52 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 18251 0 Normal Rejected auto-create or at least hint that dedicated registry needs to be created for ISV registries 2020-03-23 14:57:04 UTC

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
Note You need to log in before you can comment on or make changes to this bug.