Issue #2942 has been updated by Markus Roberts.
So the non-working one is missing macaddress_eth1, netmask_eth1, and, most interestingly, ipaddress_eth1, but has four additional values (macaddress_dummy, processor1, processor2, processor3). I'd suspect that ipaddress_eth1 is the problem. It would seem very odd to me if these changes were being made in the store config process. How is ipaddress_eth1 being set in the working case? ---------------------------------------- Bug #2942: store configs error: After adding a new external node, all clients fail with unhelpful err: "invalid ip address" http://projects.reductivelabs.com/issues/2942 Author: Rob Terhaar Status: Needs more information Priority: Normal Assigned to: Markus Roberts Category: Target version: 0.25.2 Affected version: 0.25.1 Keywords: Branch: I added our first external node to our puppetmaster today, and now I receive this message on all nodes whenever they try to refresh their catalog: err: Could not run Puppet configuration client: Parameter ip failed: Invalid IP address I know that it's related to the new external node (nagios2) because when i use the 'kill in db' script to remove nagios2 from store configs, everything works as usual. The logs do not say anything useful ether: puppetd trace/debug: http://pastebin.com/f2dad53d2 puppetmaster trace/debug: http://pastebin.com/f600413a3 -- 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.
