Problems upgrading PMM server from 2.28 to 3

I’m running PMM Server v2.28 in a Docker container. I want to upgrade to PMM 3, but when I follow the official upgrade instructions headed “Migrate PMM 2 to PMM 3” at the Percona docs web site, it fails at the first step, “Upgrade PMM 2 Server to the latest version”. Looking at the logs, I see “Could not resolve host: mirrorlist.centos.org; Unknown error” and when I dig into this, I find it’s because centos.org no longer provides a Yum repo for Centos 7. My PMM Server installation was completely broken at this point and I had to restore it from a backup of the Docker volume.

I then tried upgrading directly from 2.28 to 3, but that also failed.

Has anyone found an upgrade procedure that works for Docker installations that are using Centos 7 as the base image?

If there’s no in-place upgrade path, then is it possible to export the data from my PMM 2.28 server and import it into an empty PMM 3 server?

1 Like

To upgrade PMM 2.28 to the latest PMM 2.xx version, follow the staged approach mentioned in the documentation below.

Once you have the latest PMM 2.xx version available, you can proceed with the upgrade to PMM 3 as per the documentation.

About “Could not resolve host: [mirrorlist.centos.org](http://mirrorlist.centos.org/); Unknown error” you could check the solution mentioned here to update the repo manually as mirrorlist.centos.org doesn’t exist anymore after 2024.

1 Like

Hi Abhinav,

Thank you for the suggestions. I appreciate you taking the time to reply.

The CentOS Yum repo fix now allows the PMM-initiated upgrade to the latest 2.xx release to proceed without trashing the system, but I am left with a PMM 2.42.0 server that has “forgotten” all of the hosts and services and their histories. I presume this is because an upgrade from 2.28 directly to 2.42 hits the bug whose fix is a staged upgrade, first to 2.33 and then to 2.42.

However, the instructions for performing a staged upgrade are – unusually for Percona documentation – not very clear. None of the issues listed under the heading “Upgrade issues” seems to apply in my case, so I don’t know whether any of the fixes would help me. I would be grateful for pointers to further advice on performing a staged upgrade 2.28 => 2.33 => 2.42.

David

Hello @DavidHarper ,

let me look into it with the team and get back to you with the answer. We will find a way.

Hi Sergey,

Thanks for your kind reply. I have a copy of my live PMM system where I can test any solutions that you and your team propose.

David