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.

Description of problem:

Solve Dependencies does not add all needed packages to content view with security only filter

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

Satellite 6.10.3

How reproducible:

100%

Steps to Reproduce:
1. Provision a fresh RHEL 8.2 machine.
2. Create content view with Solve Dependencies enabled.
3. Add repositories to the content view :

Red Hat Enterprise Linux 8 for x86_64 - AppStream RPMs 8
Red Hat Enterprise Linux 8 for x86_64 - BaseOS RPMs 8

4) Add filter :

Inclusion Type : Include
Content Type : Erratum - Date and Type

Then 

Errata Type : Security

5) Publish the content view and assign it to the RHEL 8.2 machine.
6) Run "yum update --security" 



Actual results:

10 problems with dependencies.

Expected results:

Install the security errata as dependencies should be add to the content view by "Solve Dependencies"

Additional info:

Full trace of the error on the first comment.

After some internal investigation, we determined that this case was caused by a clash with RPMs already installed on the host that dependency solving cannot solve. As such, we don't see anything to fix here. In the future, if there are dependency issues in a repository even after dependency solving, investigate which RPM is missing and try adding it explicitly into the content view version.