Description of problem: When a user is on one organization (org A) and is accessing their own cv and the user switches org (org B), org A's cv is loaded in org B. Version-Release number of selected component (if applicable): 6.7.0_17 How reproducible: 100 Steps to Reproduce: 1. Create 2 different organizations 2. Log into the first org. 3. Create cv and add some repos 4. publish 5. In that cv, switch org Actual results: The same cv can still be accessed. Expected results: The different org's cv is accessed Additional info:
A fix for this issue has been provided with upstream redmine 29013. That redmine is also linked to bug 1624049. While bug 1624049 is specific to sync plans, the solution provided is generic and applies to content views and other katello resources.
Created attachment 1694521 [details] org cv Still able to see org's cv when switching to another org. The cv name isn't there, but the table still shows the content of the previous org's cv. Tested on 6.8.0 snap 2.1
Failing QA. Seeing #7 for info.
Connecting redmine issue https://projects.theforeman.org/issues/30092 from this bug
Created attachment 1699189 [details] failure when drill into version If you click content view and drill into the version and then switch org, it still show's the previous org's cv details. In this case, it's rpm, details, errata, etc which you can still click through.
Failing QA, please look at previous comment for details. Tested on 6.8.0_06
Based on last week's conversation with Lai, it seemed like a recent snap didn't show this problem.
Steps to test: 1. Create 2 different organizations 2. Log into the first org. 3. Create cv and add some repos 4. publish 5. In that cv, switch org Actual results: The different org's cv is accessed Expected results: The different org's cv is accessed Additional: drilling into the version cleared out the list of packages, erratas, etc so information from previous org's cv is not shown. Verified on 6.8.0_010
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 (Important: Satellite 6.8 release), 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-2020:4366