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

BM show log for MongoDB services does NOT reflect pbm tool errors.

Details

    • Improvement
    • Status: Open
    • Medium
    • Resolution: Unresolved
    • 2.26.0, 2.27.0, 2.28.0, 2.30.0, 2.31.0, 2.29.1
    • None
    • Backup Management*
    • Yes
    • Yes
    • No
    • Server Features
    • Hide

      #1 Setup physical MongoDB env https://confluence.percona.com/display/PMM/Set+up+PMM+and+PBM+for+MongoDB+Backups 
      #2 add wrong S3 location 
      #3 Job will fail but no logs are presented via show log feature.
      [Explain actions person need to to to reproduce the Bug. This should be very strict and precise instructions. All commands should have full syntax and all passed flags and options  ]

      Show
      #1 Setup physical MongoDB env https://confluence.percona.com/display/PMM/Set+up+PMM+and+PBM+for+MongoDB+Backups   #2 add wrong S3 location  #3 Job will fail but no logs are presented via show log feature. [Explain actions person need to to to reproduce the Bug. This should be very strict and precise instructions. All commands should have full syntax and all passed flags and options  ]

    Description

      User Impact:

      If there is any problem regarding pbm tools - our show log feature does not reflect it in the logs it clams : No logs find. Which is a problem cause our end user must have root access to the pbm tool running services which is NOT always the case.

      Steps to Reproduce:
      #1 Setup physical MongoDB env https://confluence.percona.com/display/PMM/Set+up+PMM+and+PBM+for+MongoDB+Backups 
      #2 add wrong S3 location 
      #3 Job will fail but no logs are presented via show log feature.
      [Explain actions person need to to to reproduce the Bug. This should be very strict and precise instructions. All commands should have full syntax and all passed flags and options  ]

      Actual Result:
      show log feature does not show any data

      Expected Result:
      we should be able to read the error output from pbm tool 

          status code: 301, request id: , host id:
      2022-08-22T11:32:28.000+0000 E [agentCheckup] check storage connection: storage check failed with: get S3 object header: BucketRegionError: incorrect region, the bucket is not in 'us-east-2' region at endpoint 'https://s3.amazonaws.com'

      Attachments

        Activity

          People

            michael.okoko Michael Okoko
            vojtech.koval Vojtech Koval
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:

              Smart Checklist