Bug 2168412
| Summary: | [RFE] Tie cron scheduling to recurring logics for reporting and other tasks | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | patalber |
| Component: | Reporting | Assignee: | satellite6-bugs <satellite6-bugs> |
| Status: | NEW --- | QA Contact: | Satellite QE Team <sat-qe-bz-list> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.11.5 | CC: | dsinglet, ryan.lindsay |
| Target Milestone: | Unspecified | Keywords: | FutureFeature, Triaged |
| Target Release: | Unused | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 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: | |||
Sooner the better. |
1. Proposed title of this feature request Ability to set up cron jobs via Satellite WebUI, especially for scheduling regular reporting 2. What is the nature and description of the request? We have many customers that require monthly errata reports (applicable or already applied) for their audits. We can use hammer to schedule report generation, but it's not tied to recurring logic (unless I am mistaken). There should be a mechanic within Satellite to work with cron (or recurring logics) to set up monthly (or weekly, biweekly, etc) scheduling for various tasks (reporting comes to mind first). 3. Why do you need this? (List the business requirements here) We have many customers that require monthly errata reports (applicable or already applied) for their audits. 4. How would you like to achieve this? (List the functional requirements here) Ideally tying cron to recurring logics for the scheduling piece. I could also see using Ansible via an Ansible role (if it is already present, I have simply overlooked it). 5. For each functional requirement listed, specify how Red Hat and your organization can test to confirm the requirement is successfully implemented. The customer I'm working with will happily test this within their development environment 6. Is there already an existing RFE upstream or in Red Hat Bugzilla? I believe this would qualify: https://projects.theforeman.org/issues/30180 7. Do you have any specific timeline dependencies and which release would they like to target (i.e. RHEL8.3, Sat7)? The sooner the better. 8. List any affected packages or components. I am unsure of the required components, but I would expect foreman to be involved. 9. Would you be able to assist in testing this functionality if implemented? Yes, my customer would happily assist with testing.