Important Notice: Update Process for Percona Monitoring and Management 2.38 and Earlier

We’ve received numerous reports about issues occurring with Percona Monitoring and Management (PMM) when updating to the latest version (currently 2.42.0), or updating to any version from an old version (2.37.1 and before) using the update button on the UI. 

Symptoms

PMM won’t show any notifications on the UI about new available versions if:

• You’ve been using PMM for over a year (originally installed PMM version 2.37.1 or earlier) and have been updating PMM during this time via the Update button on the UI
• You’re on version 2.37.1 or earlier

Root cause

Over a year ago, we migrated PMM’s base image from CentOS 7 to Oracle Linux 9 to enhance security and stability.

While the UI-based update process continued to work, it meant running on an older, less secure CentOS 7 image. With CentOS 7 now reaching its end of life, we’ve encountered issues where the original packages have been relocated, causing errors during the update process.

Resolution

We’re actively working on a more stable and predictable update process for PMM v3, which will address these challenges moving forward. In the meantime, to avoid these issues and ensure you’re running the latest, most secure version of PMM v2:

 

• For Docker instances: Perform a one-time Docker update to migrate to the Oracle Linux 9-based image. This update will allow you to continue using the UI Update option seamlessly in the future.
• For Non-Docker Instances (OVF/AMI): Follow the OVF/AMI upgrades instructions of the  PMM Is Getting a Modernized Enterprise-Grade Foundation blogpost.