Bug 1331167 - Content View Displayed from Different Organization while changing organizations
Summary: Content View Displayed from Different Organization while changing organizations
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Organizations and Locations
Version: 6.1.6
Hardware: All
OS: Linux
medium
medium vote
Target Milestone: Unspecified
Assignee: Walden Raines
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-27 20:19 UTC by Dustin Scott
Modified: 2020-02-14 17:45 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-07 13:30:17 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Dustin Scott 2016-04-27 20:19:56 UTC
Description of problem:

When editing or creating a new content view, or activation key, and attempting to switch organizations, the content view/activation key from the other organization (before switching) is still displayed.  IHAC who accidentally deleted the activation key from the other organization after switching to the new organization.  Dangerous!


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


How reproducible:  100%


Steps to Reproduce:
1. Navigate to Content > Activation Keys within an organization (Org1)
2. Select an existing key, or click 'New Activation Key'
3. Change Organizations (Org2)

-Alternatively-

1. Navigate to Content > Content Views within an organization (Org1)
2. Select an existing view, or click 'Create New View'
3. Change Organizations (Org2)

Actual results:

The Activation Key/Content view from the old organization (Org1) is still displayed even though we have switched to the context of Org2.


Expected results:

Because activation keys and content views are specific to an organization and cannot be shared across organizations, I would expect that when switching organizations, you would no longer have access to the key/view that you were just in.


Additional info:

Comment 3 Tomer Brisker 2017-12-07 13:30:17 UTC
Looks like this can no longer be reproduced with current releases. Please reopen if you manage to reproduce on a current release with more information.


Note You need to log in before you can comment on or make changes to this bug.