Details
-
Bug
-
Status: Done
-
Medium
-
Resolution: Fixed
-
2.31.0
-
Yes
-
2
-
Yes
-
Yes
-
No
-
Server Features
-
Description
User impact:
A user receives 500 error when starting a mongo physical backup with <2.31 client
Steps to reproduce:
- Start PMM Server 2.31
- Start PMM client 2.30 and start monitoring for MongoDB replica set
- Go to Backup Management and create an S3 storage location
- Go to the inventory tab and start Physical backup for this mongo service
Actual result:
- Internal server error received.
- Backup artifact appears in the list with BACKUP_STATUS_PENDING
Expected result:
- User should get a user-friendly message about outdated pmm client
Logs:
ERRO[2022-09-14T13:48:23.407+00:00] RPC /backup.v1beta1.Backups/StartBackup done in 18.070527ms with unexpected error: mongodb physical backup is not supported on pmm-agent "/agent_id/c56295e2-93da-4863-a4af-a4e9fc3d870a" version "2.30.0" github.com/percona/pmm/managed/services/backup.(*Service).PerformBackup /home/builder/rpm/BUILD/pmm-abad248e9467e1cfcdc7aa63052648c60c7b8398/src/github.com/percona/pmm/managed/services/backup/backup_service.go:233 github.com/percona/pmm/managed/services/management/backup.(*BackupsService).StartBackup /home/builder/rpm/BUILD/pmm-abad248e9467e1cfcdc7aa63052648c60c7b8398/src/github.com/percona/pmm/managed/services/management/backup/backups_service.go:123 github.com/percona/pmm/api/managementpb/backup._Backups_StartBackup_Handler.func1 /home/builder/rpm/BUILD/pmm-abad248e9467e1cfcdc7aa63052648c60c7b8398/src/github.com/percona/pmm/api/managementpb/backup/backups_grpc.pb.go:207 github.com/percona/pmm/api/managementpb/backup._Backups_StartBackup_Handler /home/builder/rpm/BUILD/pmm-abad248e9467e1cfcdc7aa63052648c60c7b8398/src/github.com/percona/pmm/api/managementpb/backup/backups_grpc.pb.go:209
