What I missed is that both of the nodes that are reporting the Problem state in Crowbar have the state set to "problem" in the json data stream coming from Chef.
So at least this points upstream to Chef state and not everything being happy there. ~jpr On 05/04/2014 11:54 AM, John-Paul Robinson wrote: > When I look at the data that Crowbar is pulling out of Chef on the TCP > channel the json object sent to Crowbar from Chef includes the correct > uptime value for both nodes. From what I've understood from the code, > missing uptime data is a trigger for the Problem state. _______________________________________________ Crowbar mailing list Crowbar@dell.com https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/
