-
Type:
Bug
-
Status: Done
-
Priority:
High
-
Resolution: Fixed
-
Affects Version/s: 1.14.1, 1.15.0, 1.17.1
-
Fix Version/s: 1.17.2
-
Component/s: PMM ManageD, QAN Agent
-
Labels:None
-
Story Points:0
-
Sprint:Platform Sprint 1, Platform Sprint 2
-
Needs Review:Yes
-
Needs QA:Yes
-
Needs Packaging:Yes
-
Needs Doc:Yes
User impact: User cannot see query's info after upgrade
Steps to reproduce:
- Install PMM 1.14.0
- Add RDS instances to monitoring (using credentials from PMM-1060)
- Do upgrade via docker (docker stop,rm pmm-server && docker run)
- Open Query analytics page
- Click on any query
Actual result: JS error: Failed to load resource: the server responded with a status of 404 ()
In pmm-mysqld_exporter.log in docker:
[root@5a554ec8776d opt]# tail -50 /var/log/pmm-qan-agent-9000.log
Agent config file /usr/local/percona/qan-agent/config/agent.conf does not existAgent config file /usr/local/percona/qan-agent/config/agent.conf does not existAgent config file /usr/local/percona/qan-agent/config/agent.conf does not existAgent config file /usr/local/percona/qan-agent/config/agent.conf does not exist
Expected result: Query info is displayed.
pmm-managed.log is attached
I'll re-check it with web way upgrade
P.S: everything is ok after web-way upgrade
- duplicates
-
PMM-3521 PMM Managed QAN fails to start
-
- Done
-
-
PMM-2615 Fix wrong formatting in log which appears if pmm-qan-agent process fails to start
-
- Done
-
- is duplicated by
-
PMM-3179 QAN-agent doesn't work after docker-way upgrade
-
- Done
-
-
PMM-3692 pmm-admin list returns status code 502 (text/html)
-
- Done
-
-
PMM-3693 pmm server fails to start pmm-managed after upgrade to 1.17.1
-
- Done
-
- relates to
-
PMM-3693 pmm server fails to start pmm-managed after upgrade to 1.17.1
-
- Done
-