Project

General

Profile

Actions

Bug #1250

closed

Foreman isn't registering restart failures in report summary

Added by Anonymous about 13 years ago. Updated about 13 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Reporting
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Puppet failed to restart apache, and foreman didn't register this as a failure or restart failures in the reports summary. It showed up in the detailed report. I've attached screenshots.


Files

foreman_restart_fail1.png View foreman_restart_fail1.png 66 KB Anonymous, 10/21/2011 05:05 PM
foreman_restart_fail2.png View foreman_restart_fail2.png 70.3 KB Anonymous, 10/21/2011 05:05 PM
201110241725.yaml 201110241725.yaml 16.3 KB Anonymous, 10/24/2011 01:33 PM
Actions #1

Updated by Ohad Levy about 13 years ago

which version of puppet?
any chance you can attach a sample failed report (e.g. enable reports=store and attach the report file)

thanks

Actions #2

Updated by Anonymous about 13 years ago

Version: 2.6.9-1.el5 (built rpm from source with included spec)

Recreated it with just this module enabled so you don't have to sift through my other stuff.

Actions #3

Updated by Anonymous about 13 years ago

Any idea on what's going on? This is a block for us in proceeding with foreman.

Thanks!

Actions #4

Updated by Tim Speetjens about 13 years ago

  • Assignee set to Tim Speetjens

This is an overlooked issue occurring starting with puppet 2.6.0 and onward

It's the following commit in the puppet git repo that causes it.

commit 9919b14f262c994a58eb202cda408f1b90d728e0
Author: Luke Kanies <>
Date: Wed Jan 20 02:21:54 2010 -0800

Moving Metric management to the reports
Actions #5

Updated by Ohad Levy about 13 years ago

  • Category set to Reporting
  • Target version set to 0.4.1
Actions #6

Updated by Tim Speetjens about 13 years ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF