Description of problem:

It may happen that rhc-worker-playbook receives a playbook that fails the signature check. In that case, the worker raises an exception and the execution of the playbook never starts neither is anything reported back to console.redhat.com

This happens despite the fact that infrastructure for reporting these types of problems back to console.redhat.com and is event used in other situations. For example, should playbook execution fail due Ansible not being installed on the connected hosts, this error is reported back to console.redhat.com and presented to the user (https://github.com/RedHatInsights/rhc-worker-playbook/blob/main/rhc_worker_playbook/server.py#L262)

rhc-worker-playbook should use this same mechanism to report other error cases to users, including failed signature check instead of failing silently.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:

Expected results:

Additional info: