Issue #2942 has been updated by Markus Roberts.
Assigned to changed from Dan Bode to Markus Roberts
Rob --
Can you try changing line 10 of /usr/lib/ruby/1.8/puppet/type/host.rb to:
raise Puppet::Error, "Invalid IP address: #{value.inspect}"
and try again. No need for trace/debug this time, and I really only expect
that one line of output on the client to change. That should tell us what the
bad IP looks like, which may help determine where it's coming from. Meanwhile,
I'll be exploring another angle.
-- Markus
----------------------------------------
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.
