Project

General

Profile

Bug #25

Reports might fail if puppet debuging info was enabled

Added by Ohad Levy over 9 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Puppet Reports
Target version:
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

It seems that puppet debugs doesnt send out metrics in the report?!

this causes the report list page to break, as it cant display all of the properties.

would need to look for more info

Associated revisions

Revision 0f419629 (diff)
Added by Ohad Levy over 9 years ago

fixes #53, fixes #25 and general improvment to sql delete commands

Revision 11ee3cb7 (diff)
Added by Greg Sutcliffe over 2 years ago

Fixes #25 - Use snippet flag to permit ptable snippet imports

Thanks to Chris Clonch for the original implementation - this version
is updated to account for the changes in #27

History

#1 Updated by Ohad Levy over 9 years ago

stupid workaround to remove the invalid reports:

open a console (e.g. in Foreman dir type ./script/console production) and type:

Report.find_each {|r| r.destory if r.log.metrics.nil? }

#2 Updated by Ohad Levy over 9 years ago

  • Status changed from New to Need more information
  • Target version deleted (0.1-2)

#3 Updated by Ohad Levy over 9 years ago

  • Status changed from Need more information to Assigned
  • Target version set to 0.1-2

some debug messages has no metrics, this one should be ignored as invalid reports.

#4 Updated by Ohad Levy over 9 years ago

  • Status changed from Assigned to Ready For Testing
  • % Done changed from 0 to 100

#5 Updated by Ohad Levy over 9 years ago

  • Status changed from Ready For Testing to Closed

Also available in: Atom PDF