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, execution never starts, and nothing is reported to console.redhat.com.

This happens despite the fact that infrastructure for reporting these types of problems to console.redhat.com is present, and is 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 signature validation failures, instead of failing silently.

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

All known versions of rhc and rhc-worker-playbook, including at least:

# rpm -q rhc rhc-worker-playbook
rhc-0.2.5-1.el9_5.x86_64
rhc-worker-playbook-0.1.10-1.el9_5.x86_64

How reproducible:

100%

Steps to Reproduce:

Create a remediation plan:

curl -sSH "Authorization:Bearer ${access_token}" \
    -X POST \
    -H "content-type:application/json" \
    --data-raw "$(jq < req-body.json)" \
    https://console.redhat.com/api/remediations/v1/remediations

{
  "name": "invalid-signature",
  "auto_reboot": true,
  "archived": false,
  "add": {
    "issues": [
        {
        "id": "test:invalidSignatureTasks",
        "resolution": "fix",
        "systems": ["37322c13-c257-4f8a-a129-d0c8acbe109c"]
        }
    ]
  }
}

Actual results:

The client will not report an error to console.redhat.com. When log-level = "trace" in /etc/rhc/config.toml, rhcd.service will log something like this: rhcd.log

Expected results:

An error is reported to console.redhat.com.

Additional info:

n/a