Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backup config not updated #1526

Open
ByJacob opened this issue Apr 18, 2024 · 3 comments
Open

Backup config not updated #1526

ByJacob opened this issue Apr 18, 2024 · 3 comments
Labels

Comments

@ByJacob
Copy link

ByJacob commented Apr 18, 2024

Report

  • When update secret for backup storage in kind PerconaServerMongoDB updates are not applied to PBM backup configuration
  • When update endpointUrl backup storages s3 updates are not applied to PBM backup configuration###

More about the problem

Backup configuration cannot be updated via YAML

Steps to reproduce

  1. Create cluster using PerconaServerMongoDB with s3 backup and SecretV1 and endpointUrlV1
    1. Check configutaion in backup-agent using pbm config
  2. Update PerconaServerMongoDB and use for s3 backup SecretV2 and endpointUrlV2
  3. Check configutaion in backup-agent using pbm config

Versions

  1. Kubernetes - v1.27.7
  2. Operator - percona/percona-server-mongodb-operator:1.15.0
  3. Database - percona/percona-backup-mongodb:2.3.0

Anything else?

No response

@ByJacob ByJacob added the bug label Apr 18, 2024
@spron-in
Copy link
Collaborator

Hey @ByJacob ,

so here is what I did.

  1. Deployed a cluster, configured backup with wrong endpointUrl.

Result - backup failed.

  1. Changed the endpointUrl to correct one and applied the manifest

Result - backup succeeded.

  1. Changed the secret to wrong credentials and applied.

Result - backup failed.

Apart from checking the config in the pod - do you see issues with backups?

@xcono
Copy link

xcono commented May 12, 2024

Hi, @ByJacob
I am experiencing the same issue. Were you able to find a way to update the configuration?

@ByJacob
Copy link
Author

ByJacob commented May 12, 2024

Hi, @ByJacob I am experiencing the same issue. Were you able to find a way to update the configuration?

I deleted and re-created the mongodb cluster :D You can also go into the shell cluster and change the settings with the cli tool

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants