Issues
2 of 2
Unable to upgrade using the Update Button to 2.43
Done
General
Escalation
General
Escalation
Description
How to test
upgrade from 2.42.0 to dev-latest
How to document
None
Attachments
2
is blocked by
Smart Checklist
hideCreated September 20, 2024 at 8:33 AM
Updated October 2, 2024 at 9:44 AM
Resolved October 2, 2024 at 9:44 AM
Activity
Roma NovikovSeptember 20, 2024 at 1:08 PM
The issue has been resolved for now. You can upgrade to version 2.43.0, and all instances that were in the process of upgrading will also complete the upgrade successfully.
However, the current solution is temporary. A proper fix will be included in the 2.43.1 patch release early next week.
Roma NovikovSeptember 20, 2024 at 12:07 PMEdited
With 2.43 pmm-update packages removed it’s failing on versions older than 2.42
Resolved
Users are unable to upgrade to the new version of PMM.
STR:
1. Install PMM server 2.42.0 (or earlier)
Check upgrade on home dashboard and start upgrade to 2.43.0
Actual result: Update get stuck because of the next error:
fatal: [localhost]: FAILED! => {"changed": false, "failures": [], "msg": "Depsolve Error occurred: \n Problem: package percona-postgresql14-server-1:14.13-1.el9.x86_64 from percona-ppg-14 requires percona-pg-telemetry14, but none of the providers can be installed\n - cannot install the best update candidate for package percona-postgresql14-server-1:14.10-1.el9.x86_64\n - nothing provides percona-telemetry-agent needed by percona-pg-telemetry14-1:1.0.0-1.el9.x86_64 from percona-ppg-14", "rc": 1, "results": []}
Workaround: Run “yum clean all“ command before upgrade
AMI and OVA are affected too