-
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] salt-ssh jinja import from doesn't work due to error jinja2.exceptions.TemplateNotFound #61174
Comments
This looks like a duplicate of #21370. |
I have tried workaround with extra_filerefs, but it doesn't help in my case. So it's probably different problem. It's strange, that we were using this for years without any problem, but now it's broken in version 3004. Last tested previous version is 2019.2.8, where I can confirm no problems with that. |
Hello. I made some tests and found it broke at 3003. Regards. |
I just upgraded our master from 3002.7 to 3004 and got same error calling state over salt-ssh like, all formulas worked ok when called from master->minion or on minion via salt-call with no problem. SSH command:
and i was getting error from all sls files:
I did try adding
To my suprise did get exececuted without problem and after that full formula works as well. The only thing maybe some corrupted cache after upgrade? |
I'm running into this issue now with is there a workaround that actually works for this case? and is the root cause potentially the cache dir issue that seems to be causing #60003? |
To me, it's the same as this one #60620 (that is wrongly closed as duplicates) To me, this regression get introduced in 3003 |
I'm hit by the same bug. It's incredible to me that |
@Rudd-O yeah, we just finished a migration from ansible to salt-ssh, just in time for all these |
I did not try the proposed patch but I'll try to have a look at it. I wonder if salt-ssh workgroup is working or not… |
I'm having the same issue on 3004.1 on CentOS 7. Added the patch #60620 and #60003 and neither of them solved the issue. Here's the configs we're using: /etc/salt/roster:
/etc/salt/master.d/ssh_defaults.conf
|
The latest patch updated for 3004 me tionned in #60003 worked for me |
Hello, #61895 fixes my issues. |
Still getting this with a 3005.1.4 master when I attempt a relative jinja import ( |
I believe the fix is #63184 which is not in |
so when is 3006 getting released? |
Any chance this fix get backported to 3005 one day, because right now we are stuck with 3002.9 (and cannot upgrade for the moment to 3006 since moving to onedir is quite a huge change on our side) |
? |
The bug seems gone for me in version |
Didn't notice 3007 was release, generally I wait .1 or .2 before upgrading. I had too much issue in the past with upgrading. I will try to test on my labs |
Hello @SkypLabs
My tests as described in 31531 still do not work:
|
Description
Jinja import from doesn't work with salt-ssh due to error jinja2.exceptions.TemplateNotFound. It works fine while running same setup via salt-minion, so problem is probably in salt-ssh.
Debug output:
But file /var/cache/salt/master/files/base/salt/map.jinja is present in salt master FS.
Setup
Install salt-master + salt-ssh and setup roster file. The problem occurs at Debian 9 VM with salt v3004. Tested with salt v 2019.2.8 without any problem. No minion installed at target machine, target machine is clean Debian installation.
Steps to Reproduce the behavior
Run
salt-ssh \* state.sls test
with these states:test/init.sls:
test/repo.sls:
test/map.jinja:
Expected behavior
No error and success as running salt via salt-minion.
Versions Report
salt --versions-report
``` Salt Version: Salt: 3004Dependency Versions:
cffi: Not Installed
cherrypy: Not Installed
dateutil: 2.5.3
docker-py: Not Installed
gitdb: 2.0.0
gitpython: 2.1.1
Jinja2: 2.9.4
libgit2: Not Installed
M2Crypto: Not Installed
Mako: Not Installed
msgpack: 0.6.2
msgpack-pure: Not Installed
mysql-python: Not Installed
pycparser: Not Installed
pycrypto: Not Installed
pycryptodome: 3.6.1
pygit2: Not Installed
Python: 3.5.3 (default, Apr 5 2021, 09:00:41)
python-gnupg: Not Installed
PyYAML: 3.12
PyZMQ: 17.1.2
smmap: 2.0.1
timelib: Not Installed
Tornado: 4.5.3
ZMQ: 4.2.1
System Versions:
dist: debian 9 stretch
locale: UTF-8
machine: x86_64
release: 4.9.0-16-amd64
system: Linux
version: Debian GNU/Linux 9 stretch
The text was updated successfully, but these errors were encountered: