Bug 1599072 - When multiple subscription with same product attached to the activaton-key then Repository Sets have multiplied records
Summary: When multiple subscription with same product attached to the activaton-key th...
Keywords:
Status: CLOSED DUPLICATE of bug 1575932
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Activation Keys
Version: 6.3.2
Hardware: All
OS: All
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-08 14:10 UTC by Jan Jansky
Modified: 2021-12-10 16:35 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-07-24 16:36:04 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jan Jansky 2018-07-08 14:10:30 UTC
Description of problem:
When you attach to the activation key multiple subscriptions which contains same product, for example Red Hat Enterprise Linux Server 7, then you will see 2x same repositories in Repository Sets tab.

If you attach 3 subscriptions, then 3x same repositories

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

How reproducible:
Every time.

Steps to Reproduce:
1. Create activation key
2. Attach subscription 1 with product Red Hat Enterprise Linux Server
3. Attach subscription 2 with product Red Hat Enterprise Linux Server
4. Click on Repository Sets

Actual results:
You will see multiple times same repositories entry.

Expected results:
See any repository just once

Additional info:

Even though there are multiple records shown they are all updating at once, so there is only problem in view, which confusing the customers, but records are changed on all of them when applied on just one of them.


Attaching settings on my reproducer as screenshots

Comment 3 Brad Buckingham 2018-07-24 16:36:04 UTC

*** This bug has been marked as a duplicate of bug 1575932 ***


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