Improve toubleshooting error output

asked 2016-05-31 12:49:45 -0600

rahvee gravatar image

There is one thing about puppet that constantly frustrates me, and I'd like to know if there's a better way to use puppet. I find, whenever there's an error of some kind, it's virtually impossible to figure out what caused the error. For example, I have a module that defines a bunch of virtual users and groups, and then some other module realizes a user. If you make an error (forget to realize a group that is required for a user that you realize) then the puppet agent running the virtual module throws errors about group nonexistence. There is nothing like a "stack trace" indicating that some other module was actually trying to realize a user. So the error message is misleading.

Is it possible to have puppet agent display the names and titles of resources applied? So if an error occurs, you know what caused it?

edit retag flag offensive close merge delete


if you look in the catalog, it has a set of tags that serve a similar process as a stack trace, but that only helps if your catalog compiles...

DarylW gravatar imageDarylW ( 2016-05-31 18:47:37 -0600 )edit