-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] file_roots to relative path seems broken #66588
Comments
I have the same issue, all my scripts are broken now after update. I also have downgraded to previous version. |
b0e7c62 by @hurzhurz is what caused this regression. @s0undt3ch |
This is crazy, it makes 3007.1 unusable. Could this be fixed please? |
@dtzampanakis Can you tell a bit more about how you run the master with this example config? I wanted to try it, but I can't get it working, even with 3006.8. I made a file structure like this in a test VM:
And I started the master like this: The master actually uses the file structure in /root/master-test/ for minion keys, cache, etc. It looks like the master worker threads have / as CWD. So with "./states" they actually look in "/states". Am I missing a step? Or do you use anything special to run the master, like docker or so? |
@hurzhurz this is about |
@hartwork Thanks for the hint! I somehow overlooked and also didn't expect that... |
@hurzhurz Assigned this to you assuming you are up for the task. :) |
Description
Upgrading from salt-ssh version 3007.0 (Chlorine)
to 3007.1 (Chlorine), seems to broke the file_roots that i use in my master file.
Pillars are working, but when i try to state.apply i am unable to apply any state with
Working only if i change the file_roots with an absolute path.
I installed 3006.8(Sulfur) to make it work again with relative path since i am unable to go back to 3007.0.
The text was updated successfully, but these errors were encountered: