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.
Description of problem:
Satellite delivers a set of cron jobs:
# find /etc/cron* -name '*foreman*' -o -name '*katello*'
/etc/cron.d/foreman
/etc/cron.daily/katello-repository-publish-check
/etc/cron.weekly/katello-remove-orphans
/etc/cron.weekly/katello-clean-empty-puppet-environments
Having them in Satellite's own job scheduling framework will provide several advantages:
* Recurring logics will be the onestopshop for all scheduled tasks, can also better see overlaps etc.
* All tasks have a corresponding foreman-tasks/dynflow for improved traceability
* If Sat6 is not running then also no scheduled tasks are failing due to connection problems
* During Upgrades tasks can not run to disturb upgrade process, if still possible then adding a maintenance flag to disable all recurring-logics with a global flag is easy to implement - see bz1487559
Version-Release number of selected component (if applicable):
Satellite 6.2
How reproducible:
always
Steps to Reproduce:
1. Check for periodic jobs in the Satellite UI
Actual results:
Most are somewhere in the FS
Expected results:
All jobs in one place
Additional info: