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.

Description of problem:
A External docker registry associated to a Org/Loc is shown/can be used in ALL Orgs/Locs

Version-Release number of selected component (if applicable):
@Sat6.2.0-Snap12

How reproducible:
always

Steps to Reproduce:
1. create a registry and associated it with a Loc/Org
2. switch to another Loc/Org
3. the created registry is still shown

Actual results:
org/loc context is ignored

Expected results:
org/loc context is applied

Additional info:
also when you create a container you can use a registry from differrent Loc/Org

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

Submitted for review:
https://github.com/theforeman/foreman-docker/pull/162

"also when you create a container you can use a registry from differrent Loc/Org"

That's fine, it only shows registries under your current loc/org scope. No need to limit that to the container taxonomy afaik.

Upstream bug assigned to dlobatog

Upstream bug assigned to dlobatog

Moving to POST since upstream bug http://projects.theforeman.org/issues/15098 has been closed

VERIFIED.

@satellite-6.3.0-19.0.beta.el7sat.noarch
tfm-rubygem-foreman_docker-3.1.0-1.fm1_15.el7sat.noarch

by set of hammer docker registry info/update/create commands and by UI workflows. 

>>> registries follow Org/Loc context both in UI and CLI

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/RHSA-2018:0336