From the code it seems to be executed before start_action but maybe it does
not wait for sync_after_install to finish before executing the start_action

Le dimanche 28 septembre 2014 15:29:25 UTC+2, Sebastien Estienne a écrit :
Hi Mark,

The problem is that it seems that "sync_after_install" is executed after
"start_action", so when the state.highstate runs the grains are not yet

I guess the only option is to have static grains?!

Le jeudi 25 septembre 2014 15:23:46 UTC+2, Mark van der Walle a écrit :

I have these options enabled in /etc/salt/cloud
start_action: state.highstate
sync_after_install: all

Then in my profile I have something like this:

provider: gogrid
image: Ubuntu 14.04 LTS Server (64-bit) w/ None
size: 512MB
script: Ubuntu
role: test

That works for me.

On Thursday, September 25, 2014 12:39:10 PM UTC+2, Sebastien Estienne

I'd like to run state.highstate when my server is installed with
For that purpose i m using the reactor system, it was working fine until
i started using custom grains.
Now i must sync the grains before running the state.highstate, but it
seems that the reactor execute everything in parallel, so highstate is run
before the grains are synced.
Is there a way to serialize or to say that highstate depends on the
success of saltutil.sync_grains ?

You received this message because you are subscribed to the Google Groups "Salt-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to salt-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Search Discussions

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupsalt-users @
postedSep 28, '14 at 1:39p
activeSep 28, '14 at 1:39p

1 user in discussion

Sebastien Estienne: 1 post



site design / logo © 2022 Grokbase