Add "jmx_scrape_error" check after provision/deploy

[jnogol]

Prerequisites

• Put an X between the brackets on this line if you have done all of the following:
  • Checked that your issue isn't already filled: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aidealista
  • Checked that there is not already provided the described functionality

Description

In the current role version, if the exporter scraping configuration provided is wrong, the role will execute everything and mark it as success, as the service doesn't fail but the scrape does. Adding a check after provision execution will help the role fail faster and mitigate this "silent misconfigurations".

Steps to Reproduce

1. Add wrong exporter configuration
2. Run the role in a playbook

Expected behavior: Fail, because configuration is wrong.

Actual behavior: Happily mark the execution as correct and let the exporter scrape wrongly.

Reproduces how often: Always

Versions

All