Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1385598

Summary: Any org/loc context acts as None org/loc
Product: Red Hat Satellite Reporter: Roman Plevka <rplevka>
Component: Organizations and LocationsAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6.3.0CC: dlobatog, inecas, lpramuk, oprazak
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
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: 2018-06-06 12:57:03 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 Roman Plevka 2016-10-17 11:37:24 UTC 
Description of problem:
One example for all:
create a Partition table (PT) and do not assign it to any Org/Loc.
The PT will be visible only under 'Any Org/Loc' context.
Now assign the PT to an Operating System (OS) and try to create a new host with a Default loc/org and the above OS and PT.

Actual result:
You can choose the OS (as that one is not context-limited) but you can't see the PT as it doesn't have the 'Default Org/Loc' specified.

Expected result:
If *Any org/loc* really acted as *Any*, it wouldn't matter which context we operate under.
But since it acts as *None*, we can only use it if we create the host under 'Any loc/org' - which is even not possible.

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

How reproducible:
always


Additional info:
This applies to all entities.
Comment 4 Ondřej Pražák 2017-12-04 14:21:59 UTC 
Created redmine issue http://projects.theforeman.org/issues/21854 from this bug
Comment 5 Daniel Lobato Garcia 2018-06-06 12:57:03 UTC 
This has been talked about many times. 

Any loc/org means you're able to see anything assigned to any of your organizations/locations. 

It does not mean stuff without an organization/location belongs to any. In fact, anything that can be scoped under organization/location but is not scoped, as you mention in the report (Partition Table) will not be visible to anyone but admins. 

This is by design, users can only see what is in their scopes. Admins can see unscoped stuff.

I'm closing this and the upstream bug for the time being, I can refer you to multiple discussions about the behavior if needed. Feel free to reopen if I missed something.