Restoring via PMM UI is not possible due to new interactive prompt
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.1k
- Forks
- 231
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 93
Description
Description
Currently we are facing the problem that the restoring via the PMM UI is not working due to an error (--> Check relevant logs).
This is caused by the interactive prompt which was brought within PBM 2.14 (https://docs.percona.com/percona-backup-mongodb/release-notes/2.14.0.html?h=bypass+confirmation#concurrent-streaming-for-faster-uploads-to-remote-storage-via-minio-sdk). The mentioned "R" from the log is coming from the start of the printed "Restore ..".
To fix that it would be needed that the new flag is added when executing the restore command in PMM.
We tested it also with the PBM 2.13 and there the restore still works perfectly.
Expected Results
Restoring the backup in the PMM UI is possible again
Actual Results
The restoring fails with an error
Version
PMM Version: 2.19.1
PBM Version: 2.15.0
Steps to reproduce
- Go to menu item "Backups" -> "All Backups"
- Choose one existing backup and click the three dots
- Choose "Restore from backup"
- Select your desired service
- Click "Restore"
- Check on the finished written logs
Relevant logs
pbm restore error: invalid character 'R' looking for beginning of value: invalid character 'R' looking for beginning of value
Code of Conduct
- I agree to follow Percona Community Code of Conduct
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Trace the PMM UI restore flow from the Backups page to the PMM command execution that invokes PBM. Start by checking the relevant restore logs and compare the PBM 2.14+ behavior with PBM 2.13. Done means restoring from the UI succeeds without the interactive-prompt error and the completed logs contain valid restore output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, mongodb
- Domain
- backend, database
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100