This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 2144544 - [RFE] To introduce an option of Start before while scheduling recurring jobs
Summary: [RFE] To introduce an option of Start before while scheduling recurring jobs
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Remote Execution
Version: 6.11.4
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-11-21 15:40 UTC by Sahil Bhasin
Modified: 2024-06-06 12:55 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 12:55:29 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   SAT-14108 0 None Migrated None 2024-06-06 12:55:28 UTC

Description Sahil Bhasin 2022-11-21 15:40:32 UTC 
Description of problem:

1. Proposed title of this feature request

To avoid remote executions jobs to run outside the scheduled time due to the unavailability of a Satellite server for example satellite rebooted and at the same time there were remote jobs of reboot or patching of clients which got delayed resulting in those jobs will be queued and once satellite server was back online then remote jobs got triggered which is the outside window of the host activity. 

2. What is the nature and description of the request?

Modification of the code which allows adding the "Start before" option for recurring jobs as well. 


3. Why does the customer need this? (List the business requirements here)

Current behavior:

The satellite Server has 20 reboot jobs for their hosts at the same time the satellite server was rebooted or it got shut down. Once the satellite server was back online suppose after 30 mins jobs that were supposed to do their work at the host end 30 mins before it got delayed which resulted in rebooting of the production host outside their schedule window. 

To minimize this we have an option "Start Before" at the time of scheduling future execution which can be used to prevent this but the same option is not available if we are Setting up recurring execution. So we required the "Start Before" option to be available for Set up recurring execution. 

4. How would the customer like to achieve this? (List the functional requirements here).

When going to Jobs --. Run Job --> Under Schedule Section --> Set up recurring execution that "Start before" should be available. 

5. For each functional requirement listed, specify how Red Hat and the customer 
can test to confirm the requirement is successfully implemented.

Same as Point 3. 

6. Is there already an existing RFE upstream or in Red Hat Bugzilla?

No.

7. Does the customer have any specific timeline dependencies and which release would they like to target?

As soon as possible.

8. Is the sales team involved in this request and do they have any additional input?

No.

9. List any affected packages or components.

NA.

10. Would the customer be able to assist in testing this functionality if implemented?

Yes.
Comment 1 Adam Ruzicka 2022-11-21 17:37:47 UTC 
And the expectation is that start before would be relative to expected execution time of each repetition of the job, correct? So if I have a job to run hourly with start_before set to 10 minutes it would look like this?

iteration,start_at,start_before
1,00:00:00,00:10:00
2,01:00:00,01:10:00
3,02:00:00,02:10:00
and so on?
Comment 2 Sahil Bhasin 2022-11-21 17:47:11 UTC 
Yes and if it didn't start within this time then this job should be autocancelled. This is working if we Schedule future execution jobs but the option is not available if we Set up recurring execution.
Comment 4 Paul Donohue 2023-05-11 22:28:50 UTC 
(I am the requesting customer.)

In addition to the business requirement described in #3 above (where Satellite is rebooting or otherwise unavailable when the job is scheduled to run, so the job runs later after Satellite becomes available)...

We have also run into issues where recurring Satellite jobs will run unexpectedly at random times.  For example, we ran into this during our recent Satellite 6.12->6.13 upgrade.  At some point during the upgrade, Satellite decided that it needed to run one of the scheduled reboot jobs (that was scheduled to run during an overnight maintenance window on a weekend), which then rebooted a number of production systems in the middle of a business day.  We need a way to time box this so that these reboot jobs will never run outside of our maintenance window.
Comment 7 Sanket Patil 2024-01-15 07:29:45 UTC 
Hello Team,

One of our customers has requested an update as they have waited more than 13 months and from the updates, we can sense they are getting a little impatient.

Can we please have an update on this BZ?

Also, the customer has commented to "ask the development department if a change will be made to the Satellite product to enable us to schedule remote jobs in the way we want without using our workaround?"


Regards,
Sanket Patil
Red Hat
Comment 13 Eric Helms 2024-06-06 12:55:29 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 "SAT-" 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. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.