All predefined task bunches are listed under.
Clickto open the . You can disable it or change its frequency.
Click Edit Schedule to update the schedule with your settings.
Click Delete Schedule in the upper right-hand corner to delete a schedule.
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 is displayed.
Clicking the start time links takes you back to the.
The following predefined task bunches are scheduled by default and can be configured:
Schedules auto errata updates as necessary.
(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 about autoinstallation powered by Cobbler, see Operating System Installation.
Compares configuration files as stored in configuration channels with the files stored on all configuration-enabled servers. To review comparisons, click Systems tab and select the system of interest. Go to reference:systems/system-details/sd-configuration.adoc#sd-config-compare-files.. For more information, see
Updates internal pre-computed CVE data that is used to display results on the CVE Audit.page. 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. For more information about configuring notifications for specific users, see User Details.
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 about patches, see Patches Menu.
Queues automatic updates (patches) for servers that are configured to receive them.
Gather virtual host data by running Virtual Host Gatherer configured in Virtual Host Managers. After updated data are available, the Subscription Matcher job is run.
Cleans up stale Kickstart session data.
Generates Cobbler files corresponding to Kickstart profiles created by the configuration wizard.
Synchronizes client registration data with SUSE Customer Center. By default, new, changed, or deleted client data are forwarded. To disable synchronization set in
server.susemanager.forward_registration = 0
Synchronizes with SUSE Customer Center (
mgr-sync-refresh). By default, all custom channels are also synchronized as part of this task. For more information about custom channel synchronization, see administration:custom-channels.adoc#_custom_channel_synchronization.
Cleans up outdated action chain data.
Deletes stale client action data from the file system. First it tries to complete any possibly unfinished actions by looking up the corresponding results 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.
Performs a regular check-in on clients.
Cleans up expired notification messages.
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 from the database. For more information on scheduling reboot actions, see reference:systems/system-details/sd-provisioning.adoc#sd-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 reference:systems/system-details/sd-configuration.adoc#sd-config-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
SSH Pushcontact method.
Runs a hardware refresh on all systems. This happens only monthly and can increase load on the Uyuni Server. The job uses Salt Rate Limiting. For tuning the batch size, see specialized-guides:large-deployments/tuning.adoc#java-salt-batch-size.
Deletes expired repository tokens that are used by Salt clients to download packages and metadata.
Collects authentication data from configure PAYG cloud instances.
Updates the local Reporting Database.
Collects all reporting data from peripheral Uyuni Server and update the Hub Reporting Database.
Cleans up outdated UUID records.