Repository navigation
Replies: 5 comments
|
I just upgraded salt-master to 3008.5, no changes.. here are some parts of the salt-master log when I'm launching the orchestration script through salt-api: |
|
Ok I found an ugly workaround, I created a group "salt" and added my user (forgejo_deploy) to it and I chown -R root:salt /var/cache/salt/master and chmod 775 directories and chmod 664 files under /var/cache/salt/master. I also installed a salt-minion in my salt-master jail and replaced this in my orchestration script (salt.wheel doesn't work): It is ugly but it works. I think there is definitively some problems with the various salt.utils.files.fopen( ... ) calls when an external_auth + pam user is involved |
|
I'm wondering if the problem is not in def chugid_and_umask(runas, umask, group=None): ... and the usage of getpass.getuser() . On FreeBSD, getpass.getuser() does not return the effective username. Shouldn't the function use the getuser() from the same module (which use pwd module) ? |
|
This looks like #70251, which #70330 fixes.
#70330 stops |
|
Hello @ggiesen, Thank you for those clear explanations and for the fixes. I spent the whole day yesterday racking my brain over this problem and it looks indeed the same bug..! As getpass.getuser() doens't (sometimes) return the same under FreeBSD and Linux I thought the problem might stem from there (as I had issues in the past). I am looking forward to version 3008.6 then! Cheers, |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hello,
I'm migrating from 3006 to 3008 on my FreeBSD instances. I'm using Saltstack in my CI/CD pipeline with Forgejo. The Forgejo runner is calling an orchestration script (state.orchestrate) through salt-api. My salt-master instance is running as root and salt-api too.
Here is my salt-master config:
It worked well on 3006 but since upgrade I'm having weird permissions issues involving /var/cache/salt/master/xxx. It looks like commit be97ceb is the culprit.
Part of my orchestration script looks like:
which now fail with:
Any idea what's going on? I don't understand why the salt process try to access/write/... things under /var/cache/salt/master/... as the external_auth:pam:xx user (forgejo_deplpy in my case) instead of the user under which salt-master is running (root) ?
This is on:
Thanks
All reactions