Bug 2070537 - Solve Dependencies does not add all needed packages to content view with security only filter
Summary: Solve Dependencies does not add all needed packages to content view with secu...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Views
Version: 6.10.3
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-31 12:00 UTC by Ahmed Eladawy
Modified: 2024-01-18 17:55 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-04-18 18:43:38 UTC
Target Upstream Version:
Embargoed:
aeladawy: needinfo-


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-9401 0 None None None 2024-01-18 17:55:35 UTC

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.


Note You need to log in before you can comment on or make changes to this bug.