New Salt version break

I started getting these error messages last week and I discovered it was actually caused by an incompatibility between the new version 2014.01 and an old server 0.17. In general if you’re finding strange errors, particularly with configuration that used to work, double check your version numbers match. You can always do a ‘salt machine test.version’ to check the clients version.

salt machine state.highstate
machine:
----------
	State: - no
	Name:  	states
	Function:  None
    	Result:	False
    	Comment:   No Top file or external nodes data matches found
    	Changes:

Or via salt-call state.highstate

[ERROR   ] Got a bad pillar from master, type bool, expecting dict: False
About these ads
Tagged ,

One thought on “New Salt version break

  1. Nick Booker says:

    I hit that last night.

    I also discovered another issue after doing the upgrade where it rejected with an error (whose text I can’t remember) anything of the following form in my state .sls files:

    foo:
      some-state:
        - require:
            - pkg.installed: bar
    

    salt now only seems to accept this form for requirements:

        - require:
             - pkg: bar
    

    In other words the ‘.installed’ bit doesn’t seem to be recognised any more, so you need to remove that from your slses.

    You can still use this though:

    somepkg:
      pkg.installed
    

    It’s just the .installed bit in the require (and possibly other clauses) that aren’t accepted.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Follow

Get every new post delivered to your Inbox.

Join 64 other followers