Uploaded image for project: 'Percona Monitoring and Management'
  1. Percona Monitoring and Management
  2. PMM-3089

Problem with RDS after docker way upgrade

    XMLWordPrintable

    Details

    • 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

      Description

      User impact: User cannot see query's info after upgrade
      Steps to reproduce:

      1. Install PMM 1.14.0
      2. Add RDS instances to monitoring (using credentials from PMM-1060)
      3. Do upgrade via docker (docker stop,rm pmm-server && docker run)
      4. Open Query analytics page
      5. 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

        Smart Checklist

          Attachments

            Issue Links

            duplicates

            Bug - A problem which impairs or prevents the functions of the product. PMM-3521 PMM Managed QAN fails to start

            • High - Crashes, loss of data, severe memory leak.
            • Done

            Bug - A problem which impairs or prevents the functions of the product. PMM-2615 Fix wrong formatting in log which appears if pmm-qan-agent process fails to start

            • Medium - Minor loss of function, or other problem where easy workaround is present.
            • Done
            is duplicated by

            Bug - A problem which impairs or prevents the functions of the product. PMM-3179 QAN-agent doesn't work after docker-way upgrade

            • High - Crashes, loss of data, severe memory leak.
            • Done

            Bug - A problem which impairs or prevents the functions of the product. PMM-3692 pmm-admin list returns status code 502 (text/html)

            • Medium - Minor loss of function, or other problem where easy workaround is present.
            • Done

            Bug - A problem which impairs or prevents the functions of the product. PMM-3693 pmm server fails to start pmm-managed after upgrade to 1.17.1

            • Medium - Minor loss of function, or other problem where easy workaround is present.
            • Done
            relates to

            Bug - A problem which impairs or prevents the functions of the product. PMM-3693 pmm server fails to start pmm-managed after upgrade to 1.17.1

            • Medium - Minor loss of function, or other problem where easy workaround is present.
            • Done
            mentioned in

            Page Loading...

            Page Loading...

            Page Loading...

            Page Loading...

            Page Loading...

              Activity

                People

                Assignee:
                Unassigned
                Reporter:
                nailya.kutlubaeva Nailya Kutlubaeva
                Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    Time Tracking

                    Estimated:
                    Original Estimate - Not Specified
                    Not Specified
                    Remaining:
                    Remaining Estimate - Not Specified
                    Not Specified
                    Logged:
                    Time Spent - 2 weeks, 2 days, 7 hours, 34 minutes
                    2w 2d 7h 34m