Internal documentation only

This page has been marked as draft.

Upgrade Collector from Ubuntu 18 to 20.04

Problem Copied

Ubuntu 18.04 ‘Bionic Beaver’ is “End of standard support” as of May 2023.

At the time this article was written, Ubuntu 20 (Focal Fossa) is the latest Ubuntu version the Opsview application supports.

Note: This is an in-place upgrade

• Opsview - Supported OS Compatibility Matrix

NOTE: System Administration such as this is outside the scope of support, but this guide
exists to provide insight/assistance for our customers from what we have investigated.

Solution Copied

You may either:

• Upgrade a single Collector within a Cluster at a time (complete one before moving on to the next) OR

• Upgrade all Collectors within a Cluster at the same time

Actions Copied

Important: Take a snapshot or full backup of the collector before you begin

1. Open a terminal session to the Collector server to be upgraded and switch to root.

2. Ensure Ubuntu is fully up to date:

   apt update && apt upgrade
   

3. The server must be rebooted to ensure it i running on the latest kernel. To do this, stop all opsview processes gracefully (this assumes using a bash shell):

   source /opt/opsview/lib/monit.sh
   list_services
   stop_services "${!SERVICES[@]}"
   

4. Confirm all processes are stopped

   /opt/opsview/watchdog/bin/opsview-monit summary -B
   

5. Reboot the server

   reboot
   

6. Install the Ubuntu update tool:

   apt install update-manager-core
   

7. Start the upgrade procedure:

   An example of what needs doing is in this link: do-release-upgrade.txt

   (DO NOT follow the txt file blindly but respective to your config)

   Make sure to let it replace the packages for you, and update ALL packages to pkg maintainers versions, if you do not want this then you may keep the installed version

   do-release-upgrade
   

   Reboot the box after the above completes successfully, (you will be prompted anyways)

8. When the upgrade process is complete and the server is available on the network again, reopen a terminal session to the server,sudo to root and disable the firewall (as the upgrade will re-enable it):

   ufw status
   ufw stop
   ufw disable
   

   Ensure all Opsview processes are started correctly if not

   /opt/opsview/watchdog/bin/opsview-monit summary -B
   

   Confirm all Opsview processes are all started:

   /opt/opsview/watchdog/bin/opsview-monit start all
   

9. Perform an Apply Changes in the UI to copy all required plugins from the orchestrator to the collector, at this point, the Opsview UI should show all checks on the Collector are either running or recovering, but make sure you do the below:

   /opt/opsview/deploy/bin/opsview-deploy -l <collector hostname> /opt/opsview/deploy/lib/playbooks/update-os-hosts.yml
   /opt/opsview/deploy/bin/opsview-deploy -l <collector hostname> /opt/opsview/deploy/lib/playbooks/setup-everything.yml
   /opt/opsview/deploy/bin/opsview-deploy -l <collector hostname> /opt/opsview/deploy/lib/playbooks/setup-monitoring.yml
   

   Finally, check if all packages are on focal rather than bionic

10. dpkg -l | grep -i opsview-*