Yes , this is a chef 11 feature. It runs delayed notification even after failures. It was highly debated. I had filed a ticket to make this at least configurable , but it looks like even that won't happen in chef 11. Chef 12 might have something on that line...
We just upgraded to 11.4.0 from 10.24.0, so I am not sure if this is a feature
of 11,
When chef-client runs, it will update the "Last check-in" column for the node's
status in our hosted Chef even if the run failed.
In 10.24.0 this was not the case. If the run failed, the check-in was not
updated, which was how we knew the node was having problems.
Is there a way to turn this back on, or is there supposed to be another I
should find out how the node chef-client run failed??
Archive powered by MHonArc 2.6.16.