Hide Forgot
Description of problem: Failed to lock python-pyasn1 with version lock Even though version lock file includes python-pyasn1.noarch 0:0.1.9-1.el7ost,yum update is trying to install python2-pyasn Version-Release number of selected component (if applicable): RHEL 7.2 How reproducible: Installed yum-plugin-versionlock Generated versionlock file, Generated versionlock did not include python2-crypto and python2-pyasn rpms . Executed sudo yum update , and I see that two packages are replaced [heat-admin@bmitakaoc-controller-0 ~]$ sudo yum update Loaded plugins: product-id, search-disabled-repos, subscription-manager, versionlock Resolving Dependencies --> Running transaction check ---> Package python-cryptography.x86_64 0:1.2.1-3.el7ost will be obsoleted ---> Package python-pyasn1.noarch 0:0.1.9-1.el7ost will be obsoleted ---> Package python2-cryptography.x86_64 0:1.3.1-3.el7 will be obsoleting ---> Package python2-pyasn1.noarch 0:0.1.9-7.el7 will be obsoleting --> Finished Dependency Resolution Dependencies Resolved ========================================================================================================================================================================================================== Package Arch Version Repository Size ========================================================================================================================================================================================================== Installing: python2-cryptography x86_64 1.3.1-3.el7 rhel-7-server-rpms 471 k replacing python-cryptography.x86_64 1.2.1-3.el7ost python2-pyasn1 noarch 0.1.9-7.el7 rhel-7-server-rpms 100 k replacing python-pyasn1.noarch 0.1.9-1.el7ost Transaction Summary Steps to Reproduce: Installed yum-plugin-versionlock Generated versionlock file, Generated versionlock did not include python2-crypto and python2-pyasn rpms . Executed sudo yum update , and I see that two packages are replaced [heat-admin@bmitakaoc-controller-0 ~]$ sudo yum update Loaded plugins: product-id, search-disabled-repos, subscription-manager, versionlock Resolving Dependencies --> Running transaction check ---> Package python-cryptography.x86_64 0:1.2.1-3.el7ost will be obsoleted ---> Package python-pyasn1.noarch 0:0.1.9-1.el7ost will be obsoleted ---> Package python2-cryptography.x86_64 0:1.3.1-3.el7 will be obsoleting ---> Package python2-pyasn1.noarch 0:0.1.9-7.el7 will be obsoleting --> Finished Dependency Resolution Dependencies Resolved ========================================================================================================================================================================================================== Package Arch Version Repository Size ========================================================================================================================================================================================================== Installing: python2-cryptography x86_64 1.3.1-3.el7 rhel-7-server-rpms 471 k replacing python-cryptography.x86_64 1.2.1-3.el7ost python2-pyasn1 noarch 0.1.9-7.el7 rhel-7-server-rpms 100 k replacing python-pyasn1.noarch 0.1.9-1.el7ost Transaction Summary Actual results: Expected results: Additional info:
Seems like a bug in yum or the plugin but on the off-chance it is/was a repo issue re-assignint to Release Delivery.
There is nothing we can do to fix this. Going from RHEL 7.2 to RHEL 7.3, the name of the package changed from python-pyasn1 to python2-pyasn1. The lockfile you have only specifies python-pyasn1 so the locking doesn't apply. The only workaround for this it to update the lockfile before yum updating to include an identical line for python2* as for python1*