Issue #2211 has been updated by Luke Kanies. Subject changed from puppet won't install packages if network interface does not have an IP address bound to Facter timeouts reap all subprocesses thus confusing Puppet
This is really a Facter bug, right? There's nothing we can do in Puppet to fix it. How do we switch the project? ---------------------------------------- Bug #2211: Facter timeouts reap all subprocesses thus confusing Puppet http://projects.reductivelabs.com/issues/2211 Author: John Florian Status: Accepted Priority: High Assigned to: Luke Kanies Category: Target version: 0.25.0 Complexity: Unknown Affected version: 0.24.8 Keywords: It is no longer possible to have puppet install packages via yum/rpm if the network interface is not bound to an IP address. Our use case requires using puppet in the non-daemon mode and this is possible for us because the system will have all necessary manifests and other necessary files locally. This worked just fine with 0.24.6 on Fedora 10, but began failing upon the upgrade to 0.24.8. See the attachments for failure messages and a code diff that seems to have introduced the regression. If I revert this one change, things work nicely once again. Looks like a very simple fix if it weren't for the ominous looking comment in the code. :-) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
