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 locking a specific version of a not installed package then it is not possible to lock the rest of versions of the same package. 

Version-Release number of selected component (if applicable):
dnf-plugins-core-0:4.0.18-4.el8.noarch
python3-dnf-plugin-versionlock-0:4.0.18-4.el8.noarch

How reproducible:
Trivial to reproduce.

Steps to Reproduce:
1. Lock a version of a not installed package with several versions available:
# dnf versionlock add bind-32:9.11.26-3.el8
2. Lock a package-name-spec that includes the package already locked:
# dnf versionlock add bind

Actual results:
There is a lock for the specific version of the package but no for the others.

Expected results:
After the second dnf versionlock call, locks for all versions of the not installed package.

Additional info:
This is related to https://bugzilla.redhat.com/show_bug.cgi?id=2013324.

In this case, as soon as there is a entry in the locklist that satisfies the criteria set by _match, then there is no further checking for the versions of a package that *it is not installed*. This is important as far as the semantics are to lock all available versions if the package is not installed.

PR: https://github.com/rpm-software-management/dnf-plugins-core/pull/447
test: https://github.com/rpm-software-management/ci-dnf-stack/pull/1045

Hello,

I updated the documentation for this bug, saying that dnf versionlock does not update the package list
if a specific version is locked. This change made the docs more clear.

However, I would like to ask you for more information about your use case for this bug.
Do you need this change for a specific reason?

In this case, I would mark this as RFE and work on it. If not, I would rather leave things as they are
and close this with doc update.
At this state, what you can do to avoid your issue is: every time you require to add a package, you
should delete all the other binds if you want to be sure of what is locked.

  dnf versionlock delete bind
  dnf versionlock add bind

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 (dnf-plugins-core 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/RHBA-2022:2052

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days