Sebastian Marsching

@kyle-tightest I can just give you some insight from my experience with a rather large cluster: For tables that store a lot of data per node, you want to choose...

I found a workaround to make the setup from the “Setups that (currently) don’t work” section work. 🙂 The trick is to run the GitLab runner Docker container using the...

I used the following state as a workaround to update the minions: ``` upgrade_minion: cmd.run: - name: 'apt-get update && DEBIAN_FRONTEND=noninteractive apt-get install -y --only-upgrade salt-common salt-minion' - bg: True...

@alrf Yes, the issue is still present in v3006. Luckily the [workaround](https://github.com/saltstack/salt/issues/61078#issuecomment-1003353239) still works. Without using a state, it is even easier: ``` salt cmd.run "apt-get update && DEBIAN_FRONTEND=noninteractive apt-get...

I guess it is a at least a bit irritating to add a deprecation warning before the alternative is available. In most pieces of software, a deprecation warning means: “Don’t...

The “workaround” of patching `salt-pip` or directly calling `python3 -m pip` is not a good one, because it causes the module to go into `/opt/saltstack/salt/lib/python3.10/site-packages`, when it should go into...

I just realized that the description of my workaround was both incomplete and more invasive than it had to be. Here is the correct description: First, edit `/opt/saltstack/salt/lib/python3.10/site-packages/relenv/runtime.py` and remove...

…and I found an even better, simpler workaround: In Salt 3006.8 (I haven’t tested other versions), edit `/opt/saltstack/salt/lib/python3.10/site-packages/relenv/runtime.py` and comment out line 786, which should look like this: ``` Wrapper("pip._internal.commands.install",...

I think I finally found the underlying issue and have opened an issue in the relenv project: saltstack/relenv#182 There, I also provide an alternative workaround.

For those who are interested, I was able to track this down to an issue in relenv: saltstack/relenv#182