From 5c894b9753edcde371f0a8cc18ea3433cb28fb3c Mon Sep 17 00:00:00 2001 From: Paul Tobias Date: Thu, 25 Jun 2026 21:50:53 +0700 Subject: [PATCH] test: fix failing kitchen suites by pinning salt to the image version On the *-3006* / *-3007* suites, kitchen fails on every platform while applying the salt states: 'salt' changed from '3006.17-0' to '3008.1-0' [ERROR ] ModuleNotFoundError: spec not found for the module 'site' >>>>>> Converge failed on The images ship salt 3006.17/3007.9, but salt.pkgrepo adds the salt-repo-latest repo (saltproject-rpm/, currently 3008.1) and the unpinned pkg.installed upgrades salt in place; swapping the running onedir under salt-call breaks the post-install module refresh, so the run dies. The per-version pins in test/salt/pillar/ only cover 3002/3003/3004 and set salt:release, which is no longer read by any state. Pin salt:version to the image's running version instead, so the formula keeps the installed salt. Co-authored-by: Claude --- test/salt/pillar/salt.sls | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/test/salt/pillar/salt.sls b/test/salt/pillar/salt.sls index 9338f52..f0fe517 100644 --- a/test/salt/pillar/salt.sls +++ b/test/salt/pillar/salt.sls @@ -3,6 +3,11 @@ --- salt: py_ver: 'py3' + # Pin to the salt version baked into the kitchen image so salt.minion/salt.master + # don't upgrade it to the repo's "latest" in place mid-converge — swapping the + # running onedir breaks the post-install module refresh, which raises: + # ModuleNotFoundError: spec not found for the module 'site' + version: "{{ salt['grains.get']('saltversion') }}" # Override used for FreeBSD minion service retry_options: attempts: 5