I'm seeing a undesirable change in behaviour of puppet on Fedora 10 that came about with the upgrade from 0.24.6 to 0.24.8. I have been working on a wrapper package for puppet (non-daemon) that allows it to operate reliably even when the network isn't so reliable. Each client maintains (via rsync) a local replica of all the puppet resources so that puppet on the client can continue to function correctly even if the network is down. (The clients run Fedora Live from CompactFlash and thus upon reboot look like puppet has never been run there.)
Anyway, with 0.24.6 it was possible for puppet to use yum to install packages without a network connection so long as the yum cache was preserved (on a non-volatile file system also on the CompactFlash) between boots. Now with 0.24.8 that is no longer possible. It seems dependent on having an IP address bound to eth0, which gives me trouble since these clients are using DHCP. I'm seeing the following errors that may provide some clues: Timed out seeking value for ipaddress Timed out seeking value for ipaddress Timed out seeking value for ipaddress Timed out seeking value for ipaddress warning: Could not retrieve fact ipaddress Could not autoload rpm: No child processes Could not autoload "/usr/lib/ruby/site_ruby/1.8/puppet/provider/ package/yum.rb": Could not find parent provider rpm of yum Could not autoload "/usr/lib/ruby/site_ruby/1.8/puppet/provider/ package/rpm.rb": Class ProviderRpm is already defined in Puppet::Type::Package Could not autoload rpm: Class ProviderRpm is already defined in Puppet::Type::Package Could not autoload "/usr/lib/ruby/site_ruby/1.8/puppet/provider/ package/aptrpm.rb": Could not find parent provider rpm of aptrpm Could not autoload rpm: Class ProviderRpm is already defined in Puppet::Type::Package Could not autoload "/usr/lib/ruby/site_ruby/1.8/puppet/provider/ package/up2date.rb": Could not find parent provider rpm of up2date Could not autoload rpm: Class ProviderRpm is already defined in Puppet::Type::Package Could not autoload "/usr/lib/ruby/site_ruby/1.8/puppet/provider/ package/rug.rb": Could not find parent provider rpm of rug Could not autoload rpm: Class ProviderRpm is already defined in Puppet::Type::Package Could not autoload "/usr/lib/ruby/site_ruby/1.8/puppet/provider/ package/urpmi.rb": Could not find parent provider rpm of urpmi info: mount[localhost]: Mounted / info: mount[modules]: Mounted info: mount[plugins]: Mounted err: Could not create ntp: Could not find a default provider for package Could not find a default provider for package Execution of puppet failed. If I give the interface an address, things seems to work OK, but that's not really a solution as it will cause problems when the network does come back up. Any help would be greatly appreciated. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. 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 -~----------~----~----~----~------~----~------~--~---
