Bug #9904

Content view promote of old version (or one without filters), results in old metadata

Added by Justin Sherrill almost 8 years ago. Updated over 4 years ago.

Content Views
Target version:
Bugzilla link:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:


Cloned from
Description of problem:
Unable to install a package or errata in content-host after a new publish/promote of a content view

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

How reproducible:

Steps to Reproduce:
1. Create a content view cv1 - apply some filters (to remove all packages and errata), publish, promote
2. create an activation key ak1 and attach the content view from step1
3. Register/Subscribe a content host using ak1
4. Perform the following in content host to make sure it looks good:
yum clean all && yum repolist
5. Now remove few filters in the content view cv1, publish, promote to include new packages, errata that were not present in the publish in Step 1
6. Go to Hosts -> Content Hosts -> Select the content host from Step 3 -> Attempt to install a new package / errata which is introduced with the new publish from Step 5 and not present in Step 1

Actual results:
- The task is completed in Satellite and showed GREEN
- But the errata is not actually installed in the content host. The pulp error from the content host is attached

Expected results:

Additional info:


#1 Updated by Eric Helms almost 8 years ago

  • Category set to Content Views
  • Target version set to 68
  • Legacy Backlogs Release (now unused) set to 23
  • Triaged changed from No to Yes

#2 Updated by Eric Helms almost 8 years ago

  • Target version deleted (68)

#3 Updated by Justin Sherrill almost 8 years ago

  • Status changed from New to Closed
  • Pull request added
  • Pull request deleted ()

Also available in: Atom PDF