mock doesn't obey dnf_disable_plugins config for versionlock

[arrfab]

Short description of the problem

For our build infra hosts, we are using (ansible driven) the dnf-plugin-versionlock, and ouc configuration management (ansible) is pinning some packages versions in the /etc/dnf/plugins/versionlock.list file. As we're using mock (through koji) to build packages, we had to add this to /etc/mock/site-defaults.cfg :

config_opts['dnf_disable_plugins'] = ['versionlock']  

And then builds were not conflicting (dnf) for packages in the buildroot vs host itself It worked fine (see https://issues.redhat.com/browse/CS-1707) until we upgraded from mock 2.x to 5.2 Now it seems that despite the versionlock plugin still marked as to be disabled, some packages in the buildroot weren't marked as available (but not marked as being "filtered out" though). I just decided to temporary clear the /etc/dnf/plugins/versionlock.list file on the builders and then the koji build succeeded. So my question : is mock 5.2 supposed to still disable the versionlock plugin if declared in /etc/mock/site-defaults.cfg ? As it was blocking a prod build for CentOS Stream/RHEL I haven't investigated further, as the workaround worked but creating upstream ticket to validate/invalidate what we found

Output of rpm -q mock

mock-5.2-1.el8.noarch

Steps to reproduce issue

see Jira ticket for history

[arrfab]

hmm, tried to reproduced in a "staging" env and I can't so seems that it was something else (and not mock related). Sorry for the noise and let close this one