FIX: Salt packages not versionlocked

[m0duspwnens]

It is possible that a Salt package doesn't become version locked. This can cause an error to be reported if a new Salt package has been staged in the repo and a yum update is run.

yum versionlock list

[root@jpp90man ~]# yum versionlock list
Last metadata expiration check: 0:02:25 ago on Mon 05 Aug 2024 06:30:00 PM UTC.
containerd.io-0:1.6.33-3.1.el9.*
docker-ce-3:26.1.4-1.el9.*
docker-ce-cli-1:26.1.4-1.el9.*
docker-ce-rootless-extras-0:26.1.4-1.el9.*
salt-master-0:3006.6-0.*
salt-minion-0:3006.6-0.*

yum update

Last metadata expiration check: 0:02:55 ago on Mon 05 Aug 2024 08:55:34 AM UTC.
Dependencies resolved.

Problem: package salt-master-3006.6-0.x86_64 from @System requires salt = 3006.6-0, but none of the providers can be installed
- cannot install both salt-3006.9-0.x86_64 from securityonion and salt-3006.6-0.x86_64 from @System
- cannot install both salt-3006.9-0.x86_64 from securityonion and salt-3006.6-0.x86_64 from securityonion
- cannot install the best update candidate for package salt-master-3006.6-0.x86_64
- cannot install the best update candidate for package salt-3006.6-0.x86_64
================================================================================================================================================================
Package Architecture Version Repository Size
================================================================================================================================================================
Skipping packages with conflicts:
(add '--best --allowerasing' to command line to force their upgrade):
salt x86_64 3006.9-0 securityonion 47 M

Transaction Summary
================================================================================================================================================================
Skip 1 Package

Nothing to do.
Complete!