Removing the node from MySQL resolved the issue, wish someone could
elaborate why this happens every few months?
On Tuesday, February 5, 2013, Mailing Lists mailingl...@theflux.net wrote:
I'm hoping someone else has experienced the error. The puppetmaster and
agent are on the same system and its
After investigating a little futhur I found that the yaml file for this
node (and puppetmaster) has only time stamps:
--- !ruby/object:Puppet::Node
classes: []
expiration: 2013-02-05 16:52:21.747019 -05:00
name: node
parameters:
environment: production
--- !ruby/sym _timestamp:
-
