Bug 2135792 - [RFE] Make Recurring Logic Cron lines editable
Summary: [RFE] Make Recurring Logic Cron lines editable
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Tasks Plugin
Version: 6.11.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Peter Ondrejka
URL:
Whiteboard:
: 2153082 2215898 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-10-18 12:47 UTC by Pavel Moravec
Modified: 2023-08-12 00:32 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-15128 0 None None None 2023-01-25 13:29:26 UTC

Description Pavel Moravec 2022-10-18 12:47:42 UTC
Description of problem:
Recurring logic (for at least generic jobs like Insights sync, Generate all jobs or similar) has wired Cron line that cant be edited. Sometimes the default time is in conflict with customer's requirements and should be modified.

The only way of changing the Cron line is direct foreman-rake command like:

ForemanTasks::RecurringLogic.find(5).update(:cron_line => "4 10 * * *")

This seems to work, but if nothing else it is unsupported (can't some recurring logic be broken if we spoof a schedule for it?).

Please make the Cron line editable - either via API/WebUI/hammer, or (sufficient for me) by stating the rake command is expected to work well (which we can create KCS for it and work is done).


Version-Release number of selected component (if applicable):
Sat 6.11, also 6.12


How reproducible:
100%


Steps to Reproduce:
1. see above


Actual results:
No supported way of editing the Cron line.


Expected results:
Have a supported way of editing the Cron line.


Additional info:

Comment 1 Brad Buckingham 2023-01-03 11:57:05 UTC
*** Bug 2153082 has been marked as a duplicate of this bug. ***

Comment 3 Adam Ruzicka 2023-08-11 10:29:11 UTC
*** Bug 2215898 has been marked as a duplicate of this bug. ***


Note You need to log in before you can comment on or make changes to this bug.