Notifications for client run failures incorrectly identify failing cookbook when using 'ignore_failure' property.

[brywilliamsCF]

Description

If a client run contains a resource that fails but uses the 'ignore_failure' property, notifications sent for any later client run failures will incorrectly refer to the cookbook containing the first ignored resource and not the cookbook containing the resource that actually stopped the client run and triggered the notification. Applies to Slack, ServiceNow, and Webhook notifications.

Automate Version

20190513175357

Replication Case

1. Create cookbook1 with a resource that will fail but use the 'ignore_failure' property.
2. Create cookbook2 with a resource that will fail.
3. Apply both cookbooks to a node.
4. cookbook1 will fail but the run will continue due to the use of 'ignore_failure'.
5. cookbook2 will fail, ending the run.
6. Automate will send a JSON notification. The JSON key 'exception_title' will correctly refer to the failed resource from cookbook2, but the key 'cookbook' will be cookbook1.

[vjeffrey]

@brywilliamsCF thanks for reporting the issue! I've labeled it as a bug and we will work to get the right people looking at this issue