Universal Agent 1.0.1 upgrade procedure
Universal Agent 1.0.1 is a minor release that only affects the UA Manager. There is no need to redeploy the UA clients deployed in each endpoint when upgrading from V1.0.0 to V1.0.1
UA Manager V1.0 → V1.0.1 upgrade procedure
- Back up your existing
devo-ua-deployerfolder. If you used one of the existing example inventory files (e.g.,
py3-1host-example.yaml) make sure to have a copy at hand so you can use it during the upgrade process.
- Back up your existing
- Download the new package and copy in the same directory level where the existing
devo_ua_deployerfolder is listed.
- Untar the downloaded package so that it overrides the contents of the existing
- Make sure that your inventory file still exists in
$HOME/devo-ua-deployer/inventoriesand that it still applies to your environment.
a. If your inventory file is not there or it has been overwritten, copy the existing inventory file from the backup folder created in step 1.
b. Check that the Devo domain certificates are still in place in
- Verify any configuration changes applied to the baseline configuration (e.g., enabled/disabled packs) and check whether those need to continue to be applied after the upgrade. Both packs and configurations will be updated as part of the platform upgrade process, so they might be lost after the installation is completed. If there are specific changes in the centralized configuration (
options.yaml), those changes need to be merged before running the playbook. If you want to keep those changes applied, please contact Devo to get specific support for that migration.
universal-agentplaybook using the following command (replace
your_inventory.yamlfor the actual name of your inventory file):
ansible-playbook -i inventories/your_inventory.yaml playbooks/devo-universal-agent.yaml.
- Check that the UA manager interface is accessible.
- Check that all the packs and queries are available:
a. The default packs are installed in ENABLED state. If you want to disable any of them, simply deactivate them via the administration web UI.
b. Any other additional packs should continue being available.
- Check that the data collected from the endpoints flows into Devo after the installation.
UA Manager rollback procedure
In the unlikely event of the UA Manager node ending up in a faulty status after an upgrade process, apply the following rollback procedure:
1. Restore your original
devo-ua-deployer folder from the backup location.
2. Connect to all manager hosts and ensure
duam-fleet is purged (choose the right one for your linux distro):
sudo systemctl apt remove -f duam-fleet
sudo yum remove -f duam-fleet
3. Ensure packs are removed. Step is required only on first
sudo rm -f /var/devo-ua-manager/packs
4. Change current directory to
$HOME/devo-ua-deployer and run the following command (replace
your_inventory.yaml for the actual name of your inventory file): a
nsible-playbook -i inventories/your_inventory.yaml playbooks/devo-universal-agent.yaml