Bug 1337608

Summary:	Registries ignores Org/Loc context
Product:	Red Hat Satellite	Reporter:	Lukas Pramuk <lpramuk>
Component:	Container Management	Assignee:	Daniel Lobato Garcia <dlobatog>
Status:	CLOSED ERRATA	QA Contact:	Lukas Pramuk <lpramuk>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.2.0	CC:	bbuckingham, lpramuk
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
URL:	http://projects.theforeman.org/issues/15098
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-02-21 17:01:53 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 Lukas Pramuk 2016-05-19 15:29:10 UTC

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

Comment 1 Daniel Lobato Garcia 2016-05-19 15:34:09 UTC

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

Comment 2 Daniel Lobato Garcia 2016-05-19 17:29:35 UTC

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.

Comment 4 Bryan Kearney 2016-05-19 18:15:50 UTC

Upstream bug assigned to dlobatog

Comment 5 Bryan Kearney 2016-05-19 18:15:52 UTC

Upstream bug assigned to dlobatog

Comment 7 Bryan Kearney 2016-05-27 16:16:55 UTC

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

Comment 10 Lukas Pramuk 2017-10-06 08:22:17 UTC

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

Comment 11 Bryan Kearney 2018-02-21 17:01:53 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.

https://access.redhat.com/errata/RHSA-2018:0336