if somebody else will face the problem: i made an exec with a bash one-liner to ping the $serverip until it works or the timeout occurrs (refreshonly => true). Additionally i put the network configuration class in a separate stage and let it notify the class with the exec which is in the same stage.
g, Peter Am Montag, 21. Januar 2013 20:53:43 UTC+1 schrieb Peter Bauer: > > hi, > > i am very happy with a network configuration module so far, but there is > one thing left i can not find a solution for: > if i change the network configuration e.g. from a single interface to a > bonding interface using puppet (basically if-down and if-ups), the next > steps in the run of the agent fail due to connection errors but then the > agent seems to reconnect again during the run and is able to send the > report (of course containing the errors) to the master. > Is there some way to avoid those errors (maybe by waiting for the > interface to be up)? > Can somebody please elaborate more on the connection handling of the agent: > - does it keep a TCP connection and reconnect on errors only and just for > the following steps? > > thx, > Peter > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/JT7aLD3zGlUJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
