SaltRenderError: Jinja variable the template 'salt/map.jinja' (imported on line 1) ....... #12610
Replies: 1 comment 1 reply
-
What does |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Version
2.4.50
Installation Method
Security Onion ISO image
Description
installation
Installation Type
Standalone
Location
on-prem with Internet access
Hardware Specs
Exceeds minimum requirements
CPU
12
RAM
20gb
Storage for /
200g
Storage for /nsm
1.5TB
Network Traffic Collection
span port
Network Traffic Speeds
Less than 1Gbps
Status
No, one or more services are failed (please provide detail below)
Salt Status
Yes, there are salt failures (please provide detail below)
Logs
Yes, there are additional clues in /opt/so/log/ (please provide detail below)
Detail
Salt never comes up in /opt/so/logs/salt/minion. I see; [salt.state :4325][CRITICAL][75409] Rendering SLS 'base:salt.minion' failed: Jinja variable the template 'salt/map.jinja' (imported on line 1) does not export the requested name 'UPGRADECOMMAND'; line 34
/opt/so/saltstack/defaults/salt/salt/map.jinga contains:
Note line 34 is
/opt/so/saltstack/default/salt/salt/minion.defaults.yaml contains:
/opt/so/saltstack/default/salt/salt/minion.sls begins with:
If I understand the log, salt is puking on the first line on the minion.sls file where it's trying to import the value for UPGRADECOMMAND which IS defined up in the map.jinja file. Is the system claiming that the value of UPGRADECOMMAND in the map.jinja file not being exported so it can be referenced by the minion.sls file.
This all broke after I ran
so-elastic-fleet-reset
.Guidelines
Beta Was this translation helpful? Give feedback.
All reactions