Bug 2219545

Summary:	Content View with filter add a package with broken dependency even after enabling solve dependency.
Product:	Red Hat Satellite	Reporter:	Pranjal <pbadguja>
Component:	Pulp	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED MIGRATED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.13.0	CC:	donovan.debeuckelaer, mbroekman, rlavi, sajha
Target Milestone:	Unspecified	Keywords:	MigratedToJIRA, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-06 16:23:45 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 Pranjal 2023-07-04 09:08:40 UTC

Description of problem:

Content View with filter do not resolve dependencies even if the "Solve Dependency" is enabled. 

How reproducible:

100% on all supported satellite versions.


Steps to Reproduce:
1. Create a CV with custom repository (in this case Zabbix repository) and enable "solve dependency".
2. Apply include RPM filter on the CV with package (zabbix-agent2)
3. Try to install the package (zabbix-agent2) on the client host and package installation fails with error:

Problem: cannot install the best candidate for the job
  - nothing provides zabbix-agent2-plugin-postgresql needed by zabbix-agent2-6.0.18-release1.el9.x86_64
  - nothing provides zabbix-agent2-plugin-mongodb needed by zabbix-agent2-6.0.18-release1.el9.x86_64
4. Dependency packages like zabbix-agent2-plugin-mongodb and zabbix-agent2-plugin-postgresql not getting installed as dependency.

Actual results:

Broken dependency of the package part of include filter.

Expected results:

Package getting installed with all the dependencies when "solve dependency" is enabled.

Additional info:

Comment 2 Maarten Broekman 2023-09-01 12:00:27 UTC

This applies to creating a content view from a Red Hat repository as well with an RPM filter.

Example:
1. Create a CV containing all Red Hat RHEL8 repositories.
2. Apply "Include" RPM filter on the CV with package "kernel"
3. Try to install kernel update on client host.

Error:
 Problem 1: cannot install the best update candidate for package kernel-4.18.0-425.19.2.el8_7.x86_64
  - nothing provides kernel-modules-uname-r = 4.18.0-477.21.1.el8_8.x86_64 needed by kernel-4.18.0-477.21.1.el8_8.x86_64
  - nothing provides kernel-core-uname-r = 4.18.0-477.21.1.el8_8.x86_64 needed by kernel-4.18.0-477.21.1.el8_8.x86_64
 Problem 2: cannot install the best update candidate for package kernel-4.18.0-477.13.1.el8_8.x86_64
  - nothing provides kernel-modules-uname-r = 4.18.0-477.21.1.el8_8.x86_64 needed by kernel-4.18.0-477.21.1.el8_8.x86_64
  - nothing provides kernel-core-uname-r = 4.18.0-477.21.1.el8_8.x86_64 needed by kernel-4.18.0-477.21.1.el8_8.x86_64
 Problem 3: cannot install the best update candidate for package kernel-4.18.0-477.15.1.el8_8.x86_64
  - nothing provides kernel-modules-uname-r = 4.18.0-477.21.1.el8_8.x86_64 needed by kernel-4.18.0-477.21.1.el8_8.x86_64
  - nothing provides kernel-core-uname-r = 4.18.0-477.21.1.el8_8.x86_64 needed by kernel-4.18.0-477.21.1.el8_8.x86_64
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

Actual results:

Missing dependencies.

Expected results:

Content view includes packages that the filtered RPM requires.


Additional info:
Solve dependencies increases the time to publish by orders of magnitude (10 hours with "Solve dependencies" enabled vs <20 minutes without). When adding a package in an RPM filter, have the option there to "add dependencies to filter" (essentially "rpm -qR" on the package) and including packages recursively from there. This would also help administrators identify the full scope of the filter they are adding.

Comment 3 Eric Helms 2024-06-06 16:23:45 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.