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.
I'm not sure the issue is valid. The thing here is, that `remove --oldinstallonly` does not (and according documentation is not supposed to) honor `installonly_limit` config value:
remove --oldinstallonly
Removes old installonly packages, keeping only latest versions and ver‐
sion of running kernel.
I believe that current dnf behavior is correct.
I agree with Marek that issue of functionality of `dnf remove --oldinstallonly` is not a bug. Modifying of installonly limit makes no difference to the command and it is intended.
Returning only warning when `--setopt=unknown=invalid` is used is another story and I think we should not modify behavior during lifecycle of RHEL and anyway the issue has too low severity.
I'm not sure the issue is valid. The thing here is, that `remove --oldinstallonly` does not (and according documentation is not supposed to) honor `installonly_limit` config value: remove --oldinstallonly Removes old installonly packages, keeping only latest versions and ver‐ sion of running kernel. I believe that current dnf behavior is correct.