Project

General

Profile

Actions
Copy link

Bug #4399

closed

Reports don't say which caused what

Added by Marek Hulán over 10 years ago. Updated almost 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
foreman_chef
Target version:
-
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Original issue on github https://github.com/theforeman/foreman_chef/issues/3

Puppet reports tell you which module caused which changes.
I think this could be possible with Chef as well, displaying which cookbook (even better, recipe) caused which changes in the host.

I might need a little guidance with this (and I need to set up a foreman-chef server) but I think I can do it.

The logs in chef 10 looks a bit like this:
[Sun, 09 Feb 2014 06:55:51 +0100] INFO: Processing template[/etc/default/nfs-common] action create (nfs::default line 27)
[Sun, 09 Feb 2014 06:55:51 +0100] INFO: Processing service[portmap] action start (nfs::default line 35)
[Sun, 09 Feb 2014 06:55:51 +0100] INFO: Processing service[portmap] action enable (nfs::default line 35)
[Sun, 09 Feb 2014 06:55:51 +0100] INFO: Processing service[nfslock] action stop (nfs::default line 42)
[Sun, 09 Feb 2014 06:55:51 +0100] INFO: service[nfslock] stopped

Actions
Copy link

Also available in: Atom PDF