Rendering SLS 'base:XXXXX' failed: found unexpected ':'

See original GitHub issue

Description of Issue/Question

When running “salt-call state.apply” and having a grains file “:” sign within grains options it fails with this message

[CRITICAL] Rendering SLS 'base:atlassian/jira' failed: found unexpected ':'
local:
    Data failed to compile:
----------
    Rendering SLS 'base:atlassian/jira' failed: found unexpected ':'

The grains file looks like this:

jira_java_opts:
- Dcom.sun.management.jmxremote
- Dcom.sun.management.jmxremote.port=9010
- Dcom.sun.management.jmxremote.rmi.port=9010
- Dcom.sun.management.jmxremote.local.only=true
- Dcom.sun.management.jmxremote.ssl=false
- Dcom.sun.management.jmxremote.authenticate=false
- Duser.timezone=Europe/Stockholm
- XX:+PrintGCDetails
- XX:+PrintGCDateStamps
- XX:+PrintGCTimeStamps
- XX:+PrintGCCause
- Xloggc:/var/atlassian/application-data/jira/log/atlassian-jira-gc-%t.log
- XX:+UseGCLogFileRotation
- XX:NumberOfGCLogFiles=5
- XX:GCLogFileSize=20M
- XX:ReservedCodeCacheSize=384m
- XX:+UseG1GC
- Datlassian.mail.senddisabled=true
- Datlassian.mail.fetchdisabled=true
- Datlassian.mail.popdisabled=true
jira_version: 8.1.0
jira_xms: 3g
jira_xmx: 3g
roles: jira

If I remove the : sign from all the options above it works ok OR if I downgrade to version 2015.8.8+ds-1 it also works ok (im now running 2019.2.0+ds-1)

What todo ?

Setup

(Please provide relevant configs and/or SLS files (Be sure to remove sensitive info).)

Steps to Reproduce Issue

(Include debug logs if possible and relevant.)

Versions Report

(Provided by running salt --versions-report. Please also mention any differences in master/minion versions.)

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Reactions:1
  • Comments:16 (12 by maintainers)

github_iconTop GitHub Comments

2reactions
mrichar1commented, May 8, 2019

In my case this worked fine before the upgrade, and now it is no longer working. Additionally, I’m using a saltstack provided formula, only providing the pillar data, so I don’t have control over the state to use the json filter.

Is it really the case that this type of list usage is no longer allowed in context?

1reaction
DmitryKuzmenkocommented, May 13, 2019

@mrichar1 SaltStack development team doesn’t maintain salt formulas. If you’d like you can create a new issue in the specific formula repository. Also we will be allowing a user to revert to the old behavior in 2019.2.1 release as documented here: https://docs.saltstack.com/en/latest/topics/releases/2019.2.1.html#change-to-yaml-renderer

Read more comments on GitHub >

github_iconTop Results From Across the Web

Full text of "ERIC ED512603: Multiple Literacies in the 21st ...
Research- Jon Shapiro 5 ers have found that young children at school ... We seem to have one constant in reading and that...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found