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.

Sign up for GitHub

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

Jump to bottom

Adding new backends does not trigger bucket creation (only update) #33

Open
nolancon opened this issue Aug 2, 2023 · 0 comments
Open

Adding new backends does not trigger bucket creation (only update) #33

nolancon opened this issue Aug 2, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@nolancon
Copy link
Collaborator

nolancon commented Aug 2, 2023

What happened?

When you add more S3 backends (ie create additional ProviderConfigs), buckets which have been previously created on all backends are not triggered to be created on the new backends. Only an update is triggered - this does not create new buckets, only updates buckets on backends where the bucket already exists.

How can we reproduce it?

Add additional backends/ProviderConfigs to an existing cluster, with Buckets already created on all original backends.
@nolancon nolancon added the bug Something isn't working label Aug 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@nolancon