Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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:
When using cockpit's "software update" tab, the "includepkgs" directive eventually defined in some repo is ignored. This can wreak havok on system where a thirdy party repository is enabled but filtered to provide only a very specific package subset. While cockpit is clearly affected by this problem, the root issue stems from PackageKit itself - which ignores the "includepkgs" directive.
Version-Release number of selected component (if applicable):
cockpit-packagekit-211.3-1.el8.noarch
PackageKit-1.1.12-4.el8.x86_64
How reproducible:
Enable a thirdy party repository which redefines some system package (eg: enable a fedora repository). While doing it repo-wide is clearly unwise, it can be very useful to reference only *some* packages via the "includepkgs" directive. However, clicking on the "check for update" button exposed in cockipit will lead to massive upgrades, which can wreak havoc on the entire system.
Steps to Reproduce:
1. enable a fedora repo with a specific "includepkgs" directive including a single packet
2. check that "yum update" will *not* propose a massive upgrade
3. the "check for update" button in cockpit *will* suggest upgrading 100s packages
Actual results:
Massive, dangerous upgrades are proposed
Expected results:
Only enabled/unfiltered packages should be proposed for the upgrade. More broadly, PackageKit should honor yum/dum directives as "includepkgs".
Additional info:
None
I believe the RHEL 8.3 libdnf contains this patch already.
Acceptance criteria: If includepkgs option is set for a repo, PackageKit offers only packages according to the option. This applies on all operations incl. install, upgrade, list, etc.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (yum bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHEA-2020:4510