Puppet users - Jun 2007 - Puppet starting before network is up

Lots of my puppet hosts have DHCP-assigned addresses. I''ve found, at 
least in Debian 4.0, that puppetd will often start up before the network 
interfaces are all up and running, and therefore it can''t contact the 
puppetmaster. When that happens, puppet exits immediately. I''m hacking 
around the problem with the following content in /etc/default/puppet, 
but I''m sure there''s a better solution:

====
# Puppet doesn''t like starting before it can contact the puppetmaster.
# Wait up to 30 seconds before continuing.
pserver=REDACTED
for n in `seq 1 30`; do
   ping -c 1 $pserver >& /dev/null && break
   echo -n " $n"
   sleep 1
done
DAEMON_OPTS="--server $pserver --factsync"

====
-- 
Mike Renfro  / R&D Engineer, Center for Manufacturing Research,
931 372-3601 / Tennessee Technological University -- renfro@tntech.edu

On Jun 1, 2007, at 12:54 PM, Mike Renfro wrote:
> Lots of my puppet hosts have DHCP-assigned addresses. I''ve found,
at
> least in Debian 4.0, that puppetd will often start up before the  
> network
> interfaces are all up and running, and therefore it can''t contact
the
> puppetmaster. When that happens, puppet exits immediately. I''m
hacking
> around the problem with the following content in /etc/default/puppet,
> but I''m sure there''s a better solution:
>
> ====>
> # Puppet doesn''t like starting before it can contact the
puppetmaster.
> # Wait up to 30 seconds before continuing.
> pserver=REDACTED
> for n in `seq 1 30`; do
>    ping -c 1 $pserver >& /dev/null && break
>    echo -n " $n"
>    sleep 1
> done
> DAEMON_OPTS="--server $pserver --factsync"
>
> ====
Can you file this as a bug?  It''s really a packaging problem, not a  
Puppet problem per se.

  --
  The most incomprehensible thing about the world is that it is at all
  comprehensible.     --Albert Einstein
  ---------------------------------------------------------------------
  Luke Kanies | http://reductivelabs.com | http://madstop.com