Bug 2070537

Summary:	Solve Dependencies does not add all needed packages to content view with security only filter
Product:	Red Hat Satellite	Reporter:	Ahmed Eladawy <aeladawy>
Component:	Content Views	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED NOTABUG	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	6.10.3	CC:	ahumbe, dalley, ggainey, iballou, momran
Target Milestone:	Unspecified	Flags:	aeladawy: needinfo-
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-04-18 18:43:38 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ahmed Eladawy 2022-03-31 12:00:44 UTC

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.

Comment 19 Ian Ballou 2023-04-18 18:43:38 UTC

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.