Puppet users - Aug 2010 - Puppet does not include errors in reports

Hi all.


I''m setting up Puppet Dashboard for external node and reporting
purposes,
and notice that errors on the puppet client side doesn''t get reported.
For
example, one of my classes lack a parameter, which results in the typical
"Error 400 on server [...] Could not find value for [...]", but still
the
report indicates that everything is working perfectly. I''ve found this
behavior on the reports on the local file system, so it''s not a
dashboard
issue.

Can I tune puppet to report such errors? I''m surprised that these
errors are
not reported, and are wondring what kind of error are being reported.


Best regards,
Kenneth

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On 08/26/2010 01:28 AM, Kenneth Holter wrote:
> I''m setting up Puppet Dashboard for external node and reporting
> purposes, and notice that errors on the puppet client side doesn''t
get
> reported. For example, one of my classes lack a parameter, which
> results in the typical "Error 400 on server [...] Could not find value
> for [...]", but still the report indicates that everything is working
> perfectly. I''ve found this behavior on the reports on the local
file
> system, so it''s not a dashboard issue.
Can you please confirm that you''ve looked at the YAML report file and
did not find the error listed in there? If there''s no error listed in
there, then there''s probably something wrong with Puppet. But if the
error is there and Dashboard didn''t display it, then the bug''s
with
Dashboard.

My guess is that you''re using Puppet 2.6, which Dashboard
doesn''t fully
support yet. As of Dashboard 1.0.3, it''s able to save Puppet 2.6
reports
and display some of their contents -- but much of their content (e.g.
statuses, runtimes and even success) aren''t displayed correctly. We
plan
to add this functionality in one of the next Dashboard releases, here''s
the ticket: http://projects.puppetlabs.com/issues/4514

If you''re using Puppet 0.25, then something else is going on. Please
file an issue, along with the Puppet and Dashboard versions, the
complete error messages and a full example of the report YAML so we can
debug this.

Thanks!

-igal

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Thanks for the quick reply.

Both master and client are running version 0.25.4, and I can confirm that
the YAML report file (found under the /var/lib/puppet/reports folder) does
not list the error.

I''ve created a ticket on the issue:
http://projects.reductivelabs.com/issues/4628


- Kenneth

On Thu, Aug 26, 2010 at 10:50 AM, Igal Koshevoy
<igal@pragmaticraft.com>wrote:
>  On 08/26/2010 01:28 AM, Kenneth Holter wrote:
> > I''m setting up Puppet Dashboard for external node and
reporting
> > purposes, and notice that errors on the puppet client side
doesn''t get
> > reported. For example, one of my classes lack a parameter, which
> > results in the typical "Error 400 on server [...] Could not find
value
> > for [...]", but still the report indicates that everything is
working
> > perfectly. I''ve found this behavior on the reports on the
local file
> > system, so it''s not a dashboard issue.
>
> Can you please confirm that you''ve looked at the YAML report file
and
> did not find the error listed in there? If there''s no error listed
in
> there, then there''s probably something wrong with Puppet. But if
the
> error is there and Dashboard didn''t display it, then the
bug''s with
> Dashboard.
>
> My guess is that you''re using Puppet 2.6, which Dashboard
doesn''t fully
> support yet. As of Dashboard 1.0.3, it''s able to save Puppet 2.6
reports
> and display some of their contents -- but much of their content (e.g.
> statuses, runtimes and even success) aren''t displayed correctly.
We plan
> to add this functionality in one of the next Dashboard releases,
here''s
> the ticket: http://projects.puppetlabs.com/issues/4514
>
> If you''re using Puppet 0.25, then something else is going on.
Please
> file an issue, along with the Puppet and Dashboard versions, the
> complete error messages and a full example of the report YAML so we can
> debug this.
>
> Thanks!
>
> -igal
>
-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Kenneth,

Thanks for filing the detailed bug report. I can confirm that your
report file describes no errors and even its "Failed" count is 0.
Strange.

-igal

On 08/26/2010 02:17 AM, Kenneth Holter wrote:
> Thanks for the quick reply.
>
> Both master and client are running version 0.25.4, and I can confirm
> that the YAML report file (found under the /var/lib/puppet/reports
> folder) does not list the error. 
>
> I''ve created a ticket on the
> issue: http://projects.reductivelabs.com/issues/4628
>
>
> - Kenneth 
>
> On Thu, Aug 26, 2010 at 10:50 AM, Igal Koshevoy
> <igal@pragmaticraft.com <mailto:igal@pragmaticraft.com>> wrote:
>
>      On 08/26/2010 01:28 AM, Kenneth Holter wrote:
>     > I''m setting up Puppet Dashboard for external node and
reporting
>     > purposes, and notice that errors on the puppet client side
>     doesn''t get
>     > reported. For example, one of my classes lack a parameter, which
>     > results in the typical "Error 400 on server [...] Could not
find
>     value
>     > for [...]", but still the report indicates that everything is
>     working
>     > perfectly. I''ve found this behavior on the reports on the
local file
>     > system, so it''s not a dashboard issue.
>
>     Can you please confirm that you''ve looked at the YAML report
file and
>     did not find the error listed in there? If there''s no error
listed in
>     there, then there''s probably something wrong with Puppet. But
if the
>     error is there and Dashboard didn''t display it, then the
bug''s with
>     Dashboard.
>
>     My guess is that you''re using Puppet 2.6, which Dashboard
doesn''t
>     fully
>     support yet. As of Dashboard 1.0.3, it''s able to save Puppet
2.6
>     reports
>     and display some of their contents -- but much of their content (e.g.
>     statuses, runtimes and even success) aren''t displayed
correctly.
>     We plan
>     to add this functionality in one of the next Dashboard releases,
>     here''s
>     the ticket: http://projects.puppetlabs.com/issues/4514
>
>     If you''re using Puppet 0.25, then something else is going on.
Please
>     file an issue, along with the Puppet and Dashboard versions, the
>     complete error messages and a full example of the report YAML so
>     we can
>     debug this.
>
>     Thanks!
>
>     -igal
>
>
> -- 
> 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+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.