Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2042861

Summary:	[Recurring Logic]logging for recurring logic should be more verbose
Product:	Red Hat Satellite	Reporter:	Stefan Nemeth <snemeth>
Component:	Dynflow	Assignee:	Adam Ruzicka <aruzicka>
Status:	CLOSED ERRATA	QA Contact:	Lukáš Hellebrandt <lhellebr>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.10.1	CC:	aruzicka, ehelms
Target Milestone:	6.11.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tfm-rubygem-dynflow-1.6.4	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-07-05 14:32:15 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Stefan Nemeth 2022-01-20 09:33:41 UTC

Description of problem:

If recurring logic,which looks completely fine from settings perspective, stops being executed, there is no information in production.log what actually happened. Just 'trigger_repeat'" in /var/log/production.log.


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

6.10.1

How reproducible:

Hard to reproduce to create logic which breaks after n iterations. 

Steps to Reproduce:
1. create a recurring logic
2. let it run wait until it stops


Actual results:

If recurring logic stops being executed, just 'trigger_repeat'" in /var/log/production.log. is logged, if anything

Expected results:

Have full trackback why recurring logic was not executed.

Additional info:

Creating new logic and deleting old one usually helps, but it does not provide us with root cause.

Comment 1 Adam Ruzicka 2022-02-22 12:55:42 UTC

Upstream PR was merged, moving to post.

@triage team: could we consider this for 7.0?

Comment 2 Lukáš Hellebrandt 2022-05-11 11:21:19 UTC

Verified with Sat 6.11 snap 18.5.

Created a recurring logic from template "Run Command - SSH Default" (Job Templates -> Run -> select "recurring logic"). I tried two ways to break the execution:
1) I removed foreman-proxy's SSH key from host's authorized_keys
2) Removed all roles from the user who created the recurring logic

In both cases, the log contained quite a lot of information including traceback. Attaching production.log privately.

Comment 6 errata-xmlrpc 2022-07-05 14:32:15 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: Satellite 6.11 Release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:5498