Issues
- Prevent backup/restore if connect to storage isn't successfulPBM-479Resolved issue: PBM-479Anna Fedoryshyn
- Prevent restore from incomplete backupPBM-478Resolved issue: PBM-478andrew.pogrebnoi
- Upload on GCS was broken with "InvalidArgument: Invalid argument. status code: 400"PBM-414Resolved issue: PBM-414andrew.pogrebnoi
- Very large collections experienced timeout due to full-collection scan for a preliminary countPBM-407Resolved issue: PBM-407andrew.pogrebnoi
- Mask user credentials in ps output of pbm-agentPBM-403Resolved issue: PBM-403andrew.pogrebnoi
- Add an option for choosing archive or files based dumpsPBM-395Resolved issue: PBM-395Mykola Marzhan
- Resync pbmBackups when storage location changes in configPBM-385Resolved issue: PBM-385
- Replica sets can't connect to config server when TLS is usedPBM-369Resolved issue: PBM-369
- Documentation needs to be improved. (re. SSL/TLS cert connection args)PBM-368Resolved issue: PBM-368Borys Belinsky
- Automatically raise the pbm user privileges during restorePBM-367
- PBM agent does not recognize flags --mongodb-user and --mongodb-passwordPBM-352Resolved issue: PBM-352Akira Kurogane
- Silent failure experienced when "pbm backup" executed whilst no pbm-agents startedPBM-346Resolved issue: PBM-346
- pbm should not list failed or unsuccessful backupsPBM-338Resolved issue: PBM-338andrew.pogrebnoi
- Failed backup in list of backupsPBM-325Resolved issue: PBM-325andrew.pogrebnoi
14 of 14
Prevent backup/restore if connect to storage isn't successful
Won't Do
General
Escalation
General
Escalation
Description
Environment
None
Smart Checklist
Details
Assignee
Anna FedoryshynAnna Fedoryshyn(Deactivated)Reporter
Sandra RomanchenkoSandra RomanchenkoAffects versions
Priority
Medium
Details
Details
Assignee
Anna Fedoryshyn
Anna Fedoryshyn(Deactivated)
Reporter
Sandra Romanchenko
Sandra Romanchenko
Affects versions
Priority
MediumSmart Checklist
Smart Checklist
Smart Checklist
Created May 14, 2020 at 9:45 AM
Updated March 5, 2024 at 7:14 PM
Resolved January 18, 2021 at 8:04 AM
Activity
Akira KuroganeJanuary 18, 2021 at 8:04 AM
At the time this ticket was created there was no way to check storage configuration was 100% OK without trying a "pbm backup" command. So the successful return exit code of the "pbm backup" command was misleading. It is easy to see that a user may not check the log messages in that situation; the failure would stay unknown to them.
With the addition of "pbm status" v1.4 it is now possible to check the connection status thoroughly, and the success/failure is visible in the CLI output. So the more obvious way that is available now means fixing this bug is no longer crucial.
I'll close the ticket. (If need be it can be opened again.)
When user adds (or changes) new storage for backups, pbm agent always performs sync with storage. At this stage it's already possible to determine whether connect to storage is successful or not, however user is able to start backup/restore despite of sync status.
STR:
1) add storage with incorrect creds, endpointUrl, bucket
2) sync fails
Actual result: User starts backup - successful status is returned, so only when user decides to check logs, he'll find that connect to storage isn't OK.
Expected result: User is unable to start backup/restore, error message is returned asking to re-check storage connection.