Issues
- Unable to upgrade using the Update Button to 2.43PMM-13384Resolved issue: PMM-13384Puneet Kala
- pmm-dump fails to upload the file to SFTPPMM-12884Resolved issue: PMM-12884Jiří Čtvrtka
- PMM Dump page needs more detailsPMM-12883
- Changing PMM settings shows successful notification even when it failsPMM-12881Resolved issue: PMM-12881ioana.maniga
- pmm-admin --tls-skip-verify does not work when x509 authentication is usedPMM-12880Resolved issue: PMM-12880Jiří Čtvrtka
- QAN - No queries available for this combination of filters in the selected time framePMM-12874Resolved issue: PMM-12874
- Importing data to PMM should not require Admin privsPMM-12867
- Group Replication dashboard should allow filtering on cluster namePMM-12853
- CurrentOp metric not visiblePMM-12848Resolved issue: PMM-12848Nurlan Moldomurov
- Enable users to specify the connection timeout for exporters.PMM-12832
- Updating PostgreSQL database from 11 to 14 may fail if supervisor is able to start PostgreSQL first before the updaterPMM-12817Resolved issue: PMM-12817
- "Skip TLS certificate and hostname validation" flag isn't working.PMM-12807Resolved issue: PMM-12807Nurlan Moldomurov
- Logs get filled with `CommandNotSupportOnView` messagePMM-12805Resolved issue: PMM-12805Jiří Čtvrtka
- I/O error: Broken pipe, while writing to socketPMM-12788Resolved issue: PMM-12788
- pq: remaining connection slots are reserved for non-replication superuser connectionsPMM-12787Aaditya Dubey
- PMM server High Memory usage after upgrading from 2.39 to 2.41.0 versionPMM-12786Resolved issue: PMM-12786
- VictoriaMetrics scrape configuration contains unsupported paramsPMM-12785Resolved issue: PMM-12785Nurlan Moldomurov
- QAN - invalid GetActionRequest.ActionId: value length must be at least 1 runesPMM-12784Resolved issue: PMM-12784Matej Kubinec
- permission denied for function pg_ls_waldirPMM-12781Resolved issue: PMM-12781Nurlan Moldomurov
- About the need of improving PMM Tables - Alert rule templates tablePMM-12780
- Unclear/wrong '0001-01-01' creation date in "Alert rule templates"PMM-12779
- Permission denied for function pg_ls_waldir error in pmm-agent.log in PMM serverPMM-12759
- PMM agent stoped working after restarting of PMM serverPMM-12743Resolved issue: PMM-12743
- Stop internal VM if external VM is usedPMM-12740
- QAN - pagination is not workingPMM-12725Resolved issue: PMM-12725Nurlan Moldomurov
- Improve filter functionality on the Backup pagesPMM-12719
- [Cluster View - Search] FE is continuously searching for few search terms if a user changes input too quicklyPMM-12714Matej Kubinec
- Change default value for Autodiscovery from 0 to 10PMM-12709Resolved issue: PMM-12709Matej Kubinec
- PMM Dump : delete followed by immediate download heads to 404PMM-12683Resolved issue: PMM-12683Dora Cretu
- PMM Dump : QAN data missing when multiple or all services (default) selectedPMM-12682Resolved issue: PMM-12682Artem Gavrilov
- Typo in MongoDB cluster summary dashboardPMM-12658Resolved issue: PMM-12658Yash Sartanpara
- Change error output from pmm-admin for autodiscovery option to more user-friendlyPMM-12651Resolved issue: PMM-12651Jiří Čtvrtka
- Remove pmm-managed-dev database from -exclude-databases flagPMM-12647
- External components (Clickhouse,PG, VM) improvementsPMM-12642Resolved issue: PMM-12642
- [QAA] Automate verification of upgrade in Progress MessagePMM-12636vasyl.yurkovych
- [QAA] Automate DbaaS DeprecationPMM-12635Resolved issue: PMM-12635vasyl.yurkovych
- Metric grafana_custom_dashboards_pillar_combined returns incorrect valuePMM-12612
- Metric grafana_custom_dashboards_pillar_combined returns incorrect valuePMM-12611Resolved issue: PMM-12611
- External services show with an incorrect status in the PMM inventoryPMM-12478Alex Demidoff
- pmm-agent searches tries to access a local database in mongosPMM-12276Resolved issue: PMM-12276Nurlan Moldomurov
- Collection from `runtime_mysql_servers` table requires admin privilegesPMM-9602
- PMM Home Dashboard - Link on DB QPS (click to go to: MySQL Overview - <NODE_NAME>) is going to the wrong nodePMM-8238Resolved issue: PMM-8238
- Add tooltips to MySQL MyRocks Metrics dashboardPMM-4558
43 of 43
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
hide
Created 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