Depot Client Maintenance
This guide covers keeping your Depot Client installation and repository configurations current.
Updating the Depot Client
The Depot Client is distributed as an RPM package. Update it using DNF:
sudo dnf update depot
Check your current version:
depot --version
Refreshing Repository Configuration
The depot refresh command regenerates the repository configuration files in /etc/yum.repos.d/ for all enabled products, based on the current host configuration and the latest metadata from the Depot server. Run it after credential changes, or any time you want to ensure your configurations are current.
To trigger a refresh manually:
sudo depot refresh
depot refresh updates the repository configuration files for enabled products. It does not modify the DNF/YUM package metadata caches. To refresh package metadata, see Refreshing Repository Metadata below.
If depot refresh reports that refresh is disabled, re-enable the refresh functionality with sudo depot refresh --enable (and disable it with sudo depot refresh --disable). This toggle is separate from the systemd timer described below.
Automatic Refresh with systemd
The Depot Client includes a systemd timer (depot-refresh.timer) that automatically runs depot refresh on a schedule. The timer is enabled by default during installation and operates on its own.
The timer runs on the following schedule:
- Executes 30 seconds after system startup
- Runs periodically every 7 days
- Includes a randomized delay of up to 1 hour to distribute load
- Persists through system reboots
Managing the Timer
Check the timer status:
sudo systemctl status depot-refresh.timer
View the timer schedule and next run time:
sudo systemctl list-timers depot-refresh.timer
View refresh logs:
sudo journalctl -u depot-refresh
If needed, the timer can be disabled or re-enabled:
# Disable the automatic refresh timer
sudo systemctl disable --now depot-refresh.timer
# Re-enable the automatic refresh timer
sudo systemctl enable --now depot-refresh.timer
Updating Repository Credentials
If your organization's access token is regenerated, you'll need to update your Depot Client credentials:
sudo depot login --force -u YOUR_USERNAME -t YOUR_TOKEN
The --force flag is required to overwrite existing credentials. After re-logging in, the client automatically runs depot refresh to update all enabled product configurations with the new credentials.
Get your current credentials from https://portal.ciq.com/token.
Updating Manual Repository Configurations
If you configured repositories manually (without the Depot Client), update the credentials in each repository file:
sudo vi /etc/yum.repos.d/ciq-*.repo
Update the username and password fields with your new credentials.
Refreshing Repository Metadata
Force a refresh of repository metadata:
sudo dnf clean metadata
sudo dnf makecache
Checking Product Status
Verify which products are currently enabled:
sudo depot list --enabled
Debugging Issues
Use debug mode for verbose output when troubleshooting:
sudo depot --debug list
See Also
- Installation Guide: Installing the Depot Client
- Setting Up Host: Configuring repositories
- Rsync Mirroring: Maintaining local mirrors