[Bug]: yum versionlock via yumpkg is looping to set packages on hold because it does not differentiate between i686 and x86_64

[maltris]

I have only CentOS 7 and salt 3006.x for testing right now, the bug report form (issue) suggests to create this instead as a discussion.

I see the behaviour that using yumpkg and hold: True results in changes on every run if the installed packages are suffixed with ".i686" to install that specific arch package in a multiarch setup.

          ID: pkg_dependencies
    Function: pkg.installed
      Result: True
     Comment: All specified packages are already installed.
              Package glibc.i686 is now being held..
    Started: 18:05:13.231843
    Duration: 1683.291 ms
     Changes:   
              ----------
              glibc-devel.i686:
                  ----------
                  new:
                      hold
                  old:

At this point the package was already held and is listed in yum versionlock status as well as the versionlock file:

# yum versionlock status
Geladene Plugins: fastestmirror, versionlock
Loading mirror speeds from cached hostfile
0:glibc-2.17-326.el7_9.3.*

# cat pluginconf.d/versionlock.list 

# Added locks on Thu Jan 29 18:12:49 2026
0:glibc-2.17-157.el7_3.1.*

Ofc I have tried a simple search to find similar issues, but could find nothing. I therefore also believe that this still exists in newer versions of salt in combination with CentOS Stream 9. Any good leads on how to proceed with this?