Bug 2102054

Summary:	Invalid signature error not reported to playbook dispatcher
Product:	Red Hat Enterprise Linux 9	Reporter:	Jozef Hartinger <jharting>
Component:	rhc-worker-playbook	Assignee:	CSI Client Tools Bugs <csi-client-tools-bugs>
Status:	CLOSED MIGRATED	QA Contact:	Red Hat subscription-manager QE Team <rhsm-qe>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	ahitacat, gchamoul
Target Milestone:	rc	Keywords:	FutureFeature, MigratedToJIRA
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	SCRUB_20220630
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-07 13:12:27 UTC	Type:	Story
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jozef Hartinger 2022-06-29 08:40:02 UTC

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:

Comment 2 RHEL Program Management 2023-09-07 13:06:41 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 3 RHEL Program Management 2023-09-07 13:12:27 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues.