Underall predefined task bunches are listed.
Click ato open its where you can disable it or change the frequency. Click Edit Schedule to update the schedule with your settings. To delete a schedule, click Delete Schedule in the upper right-hand corner.
Only disable or delete a schedule if you are absolutely certain this is necessary as they are essential for Uyuni to work properly.
If you click a bunch name, a list of runs of that bunch type and their status will be displayed. Clicking the start time links takes you back to the.
For example, the following predefined task bunches are scheduled by default and can be configured:
(Re)generates repository metadata files.
Cleans up stale package change log and monitoring time series data from the database.
Clears task engine (taskomatic) history data older than a specified number of days, depending on the job type, from the database.
Synchronizes distribution and profile data from Uyuni to Cobbler. For more information refer to: Cobbler
Compares configuration files as stored in configuration channels with the files stored on all configuration-enabled servers. To review comparisons, click the Compare Files.tab and click the system of interest. Go to . For more information, refer to:
Updates internal pre-computed CVE data that is used to display results on the CVE Auditpage. Search results in the page are updated to the last run of this schedule). For more information, see:
Sends daily report e-mails to relevant addresses. To learn more about how to configure notifications for specific users, see: User Preferences
Updates internal patch cache database tables, which are used to look up packages that need updates for each server. Also, this sends notification emails to users that might be interested in certain patches. For more information on patches, see: Patches
Queues automatic updates (patches) for servers that are configured to receive them.
Cleans up stale kickstart session data.
Generates Cobbler files corresponding to Kickstart profiles created by the configuration wizard.
mgr-registercommand, which synchronizes client registration data with NCC (new, changed or deleted clients' data are forwarded).
the default time at which the start of synchronization with SUSE Customer Center (SCC) takes place (
deletes stale client action data from the file system. First it tries to complete any possibly unfinished actions by looking up the corresponding results; these results are stored in the Salt job cache. An unfinished action can occur if the server has missed the results of the action. For successfully completed actions it removes artifacts such as executed script files.
deletes stale package files from the file system.
any reboot actions pending for more than six hours are marked as failed and associated data is cleaned up in the database. For more information on scheduling reboot actions, see: Power Management
Cleans up Sandbox configuration files and channels that are older than the sandbox_lifetime configuration parameter (3 days by default). Sandbox files are those imported from systems or files under development. For more information, see: Add Files
cleans up stale Web interface sessions, typically data that is temporarily stored when a user logs in and then closes the browser before logging out.
prompts clients to check in with Uyuni via SSH if they are configured with a.
deletes expired repository tokens that are used by Salt clients to download packages and metadata.