Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionFred van Zwieten
2015-09-07 19:33:10 UTC
Description of problem:
Currently, packages selected for inclusion into a content view during publish do not include dependent packages which is a big annoyance because this dependency checking must now be done manually which is a lot of work, especially if it is a multilevel dependency.
Version-Release number of selected component (if applicable):
How reproducible:
6.
Steps to Reproduce:
example:
1. create content view with rhel 7Server
2. create include filter on all base packages
3. create include filter on errata up to 1-apr-2015
4. create include filter on package redhat-access-insights
5. publish & promote contentview
6. subscribe content host to this content views repo's
7. try to install redhat-access-insights
8. look at dependency errors and try to resolve based on info
9. keep doning until all dependencies are resolved.
Actual results:
yum dependency errors
Expected results:
able to install packages with all dependencies resolved
Additional info:
If dependency cannot be resolved due to missing dependent packages in included repo's the publish task should fail with a clear explanation why it failed.