Description
Environment
Activity
Aaditya Dubey October 10, 2024 at 11:58 AMEdited
Hi
This issue is now verified.
I’ve tested this issue on GKE by following the steps here at
There are two aspects of this issue:
If we pass the password to
secret.yaml
having special characters in it Eg:backup^%&458GH
without encoding just plain string as mentioned:MONGODB_BACKUP_PASSWORD: backup^%&458GH
it throws the following error:If we pass the password to
secret.yaml
having special characters in it Eg:backup%5E%25%26458GH
with percent-encoding:MONGODB_BACKUP_PASSWORD: backup%5E%25%26458GH
It throws errors like:Another error we observed is:
Please note that I’ve tested the PBM without the operator with multiple different passwords containing special characters, which works perfectly fine after doing percent-encoding, so it looks like an issue from the operator’s side.
Aaditya Dubey October 7, 2024 at 10:46 AM
Hi
Thank you for the report.
Please share the complete reproducible steps.
In MongoDB operator 1.16.0, the pbm breaks when the backup password has special characters in it:
for example, the backup user has below password:
connection works with the db after specifying #'s hex - %23:
When taking an on-demand backup backup2:
From pbm agent log:
backup stuck at a point (first backup backup1 was taken with the normal password):
Can you please check and correct the operator to handle the password with special character’s for PBM?