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

Nas gateway: InvalidBucketState: Object Lock configuration cannot be enabled on existing buckets #9585

Closed
zzzuzik opened this issue May 13, 2020 · 5 comments

Comments

@zzzuzik
Copy link

zzzuzik commented May 13, 2020

Hello,

Minio with the most latest version. I'm getting:

InvalidBucketState: Object Lock configuration cannot be enabled on existing buckets

while trying to create a new bucket through terraform.
This is nasgateway. I see #9548 commit were made for lock/gateway.
Will it take care of this issue? If yes, could you please cut a new release.
Thank you for the Minio

@kannappanr
Copy link
Contributor

@zzzuzik I tested the latest master and did not see this issue. So, you will not see this issue with the next release. We will be making a release in a couple of days. We will send out a message on https://slack.min.io when we make a release. Closing this issue as answered, please feel free to reach out to us at https://slack.min.io if you have further questions

@zzzuzik
Copy link
Author

zzzuzik commented May 16, 2020

Just upgraded to the latest release. It starts failing with:
DEBUG: Validate Response s3/GetObjectLockConfiguration failed, attempt 0/25, error NotImplemented: A header you provided implies functionality that is not implemented

looks like the terraform-aws waits for different error MethodNotAllowed
https://github.com/terraform-providers/terraform-provider-aws/blob/14c139d67eb1129c790d2bcd516ef7e40b440eac/aws/resource_aws_s3_bucket.go#L2680

@harshavardhana
Copy link
Member

Just upgraded to the latest release. It starts failing with:
DEBUG: Validate Response s3/GetObjectLockConfiguration failed, attempt 0/25, error NotImplemented: A header you provided implies functionality that is not implemented

looks like the terraform-aws waits for different error MethodNotAllowed
https://github.com/terraform-providers/terraform-provider-aws/blob/14c139d67eb1129c790d2bcd516ef7e40b440eac/aws/resource_aws_s3_bucket.go#L2680

That doesn't look correct @zzzuzik NotImplemented is a proper error and it shall not be implemented with NAS gateway/FS mode in MinIO - it should be properly ignored on the terraform side.

@harshavardhana
Copy link
Member

hashicorp/terraform-provider-aws#13366 sent the fix here @zzzuzik

@zzzuzik
Copy link
Author

zzzuzik commented May 16, 2020

@harshavardhana thank you for the light speed feedback. Will track it in the terraform provider. Cheers!

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 7, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants