Issue #3942 has been reported by seph seph.
----------------------------------------
Bug #3942: inadequate error messages for malformed host types
http://projects.puppetlabs.com/issues/3942
Author: seph seph
Status: Unreviewed
Priority: Normal
Assigned to:
Category:
Target version:
Affected version: 0.25.4
Keywords:
Branch:
When puppet encounters a malformed host type, say because the variable for the
ip address is unassigned, it produces a hard to debug error messages. Using
lucid, and the puppet packaged for it:
r...@dell-r610-4v0hsl1:~# cat /tmp/host.pp
host{ "test":
ip => "",
}
r...@dell-r610-4v0hsl1:~# puppet --version
0.25.4
r...@dell-r610-4v0hsl1:~# puppet -v /tmp/host.pp
info: Loading facts in acpi_available
info: Loading facts in interfaces
Parameter ip failed: Invalid IP address
I'd really like to see the name of the offending file, and the line. And
something me it was a host type.
This bug feels pretty much identical to #2633 (which I created awhile ago).
Which makes me think there's a meta issue around error messages, and not just
these ad hoc bugs. Judging from the diff in #2633, this ends up being related
to raising errors, and not calling self.fail? But I'm kinda grasping at straws.
I suspect someone with more ruby and puppet internals knowledge could grep for
cases of this.
--
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://projects.puppetlabs.com/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.
