Bug 1784254

Summary:	Static recurring job failed to schedule on 2nd iteration if any of the target host record is invalid.
Product:	Red Hat Satellite	Reporter:	Alexey Masolov <amasolov>
Component:	Remote Execution	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED ERRATA	QA Contact:	Peter Ondrejka <pondrejk>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.6.0	CC:	aruzicka, hyu, inecas, jbhatia, lstejska
Target Milestone:	6.11.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tfm-rubygem-foreman_remote_execution-4.5.1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-07-05 14:27:59 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 Alexey Masolov 2019-12-17 05:37:21 UTC

Description of problem:
If the first run of a recurring job fails (hosts are not available for example) then it won't get rescheduled. The next occurrence time reflects the first run. 

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

How reproducible:
It can be successful on some deployments. Couldn't find the difference. 


Steps to Reproduce:
1. Create a new recurring job and include unavailable hosts. 
2. Wait for the first run and check its next time 

Expected results:
The job will be rescheduled even if the first run failed.

Comment 9 Adam Ruzicka 2021-09-06 11:45:57 UTC

It feels like this might be actually a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1944322 and therefore fixed in tfm-rubygem-foreman_remote_execution-4.5.1. If it really is so, then it should be already fixed since 6.10 snap 12. Moving to on_dev to have it go through qa process with next snap.

Comment 11 Peter Ondrejka 2022-01-14 14:57:30 UTC

Verified on Satellite 7 snap4, recurring job is correctly rescheduled and retriggered even if there are unavailable hosts

Comment 14 errata-xmlrpc 2022-07-05 14:27:59 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