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:
dnf has some foot-shooting protection to avoid screwing up your system too hard, where it states "The operation would result in removing the following protected packages". Unfortunately, this protection doesn't extend to the "subscription-manager" package on RHEL.
This should really be in the protected list, as without it, you lose access to the repos and hence cannot reinstall it. It's almost functionally equivalent to removing dnf itself.
Version-Release number of selected component (if applicable):
dnf-4.10.0-5.el9_0.noarch
How reproducible:
100%
Steps to Reproduce:
1. sudo dnf remove subscription-manager
Actual results:
subscription-manager is removed, breaking dnf.
Expected results:
dnf refuses to proceed since subscription-manager is essential for its operation.
Additional info:
This is a bit of an odd corner case, but since dnf has the "protected packages" mechanism, I figured I'd report it.
We stumbled upon this when testing correct behaviour of our software in the absence of python3-gobject. Removing that also nuked subscription-manager, which we didn't notice until dnf stopped working. :)
DNF already has an mechanism how to protect particular packages - see dnf.conf(5) and look for `protected_packages` (there are packages that already use it and drop files into /etc/dnf/protected.d directory, e.g. sudo, systemd).
So let me re-assign the bug to subscription-manager. They can decide whether they want to leverage this mechanism and have their package protected.
Comment 2RHEL Program Management
2023-09-22 14:02:41 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 3RHEL Program Management
2023-09-22 14:04:09 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 "RHEL-" 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.