Project

General

Profile

Actions

Bug #9566

closed

Activation key connected to update composite content view includes non-existing repositories

Added by Justin Sherrill almost 10 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Category:
Web UI
Target version:
Difficulty:
medium
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1196156
Description of problem:
After replacing a component in a Composite Content View the Activation key still includes references to the old repositories.

In the example below the composite content view has a component replaced changes the used repository from "HOICI-1_0_0-ci" to "HOICI-1_0_0-sp17".
But as can be seen after a clean registering, the old content is still available.

  1. subscription-manager register --org="Hilti" --activationkey="TestActKey" --force
  1. yum repolist
    Loaded plugins: changelog, downloadonly, package_upload, product-id, security, subscription-manager
    This system is receiving updates from Red Hat Subscription Management.
    https://li-lc-1017.hag.hilti.com/pulp/repos/Hilti/Library/Test/custom/HOICI/HOICI-1_0_0-ci/repodata/repomd.xml: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not Found"
    Trying other mirror.
    Hilti_HOICI_HOICI-1_0_0-sp17 | 2.1 kB 00:00
    Hilti_HOICI_HOICI-1_0_0-sp17/primary | 3.8 kB 00:00
    Hilti_HOICI_HOICI-1_0_0-sp17 16/16
    repo id repo name status
    Hilti_HOICI_HOICI-1_0_0-ci HOICI-1.0.0-ci 312
    Hilti_HOICI_HOICI-1_0_0-sp17 HOICI-1.0.0-sp17 16
    repolist: 328

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

How reproducible:

Steps to Reproduce:
1. Create Product TestProduct
2. Create repo TestRepoA in TestProduct
3. Create repo TestRepoB in TestProduct
4. Create Contentview TestViewA
5. Assign repository TestProduct/TestRepoA
6. Publish TestViewB
7. Create Contentview TestViewB
8. Assign repository TestProduct/TestRepoB
9. Publish TestViewB
10. Create Composite Content View TestComposite
11. Add Component TestViewA to TestComposite
12. Publish TestComposite
13. Create Activation Key TestActKey
14. Assign TestComposite to TestActKey
15. Assign Subscription TestProduct to TestActKey
16. Client: Register with subscription-manager register --org="MyOrg" --activationkey="TestActKey" --force
17. Client: List repos subscription-manager repos --list
18. Add Component TestViewB to TestComposite
19. Remove Component TestViewA to TestComposite
20. Publish TestComposite
21. Client: Register with subscription-manager register --org="MyOrg" --activationkey="TestActKey" --force
22. Client: List repos subscription-manager repos --list

Actual results:
The list contains also the obsolete (and not accessible) repositories of TestProduct/TestRepoA.
Updating yum metaata fails, e.g. yum repolist

Expected results:
Only TestProduct/TestRepoB is availabel to the client
yum repolist works

Additional info:


Related issues 1 (0 open1 closed)

Copied to Katello - Bug #25881: Activation key connected to update composite content view includes non-existing repositoriesDuplicateSamir JhaActions
Actions

Also available in: Atom PDF