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

Deleted COS Bucket name reuse info missing in provider registry documentation. #4819

Closed
umarali-nagoor opened this issue Sep 25, 2023 · 3 comments
Labels
documentation enhancement service/Object Storage Issues related to Cloud Object Storage

Comments

@umarali-nagoor
Copy link
Collaborator

Its been observed that many customers query about time to wait to re-use the cos bucket name after its deletion.

one of the sample customer query


Case Short Description:
SAP HANA Backup COS Script Error: Bucket Name already exists, even after resource deletion

Case Description:
Please provide the following information to assist with resolving your case.
We will use the information below to begin investigating your issue/question:

Trying to deploy the scripts associated with COS and keep running into an error where it says the bucket already exists - due to an earlier Schematics plan failure. I have since tried to delete the resources associated with the workspace, double checking in my Resource List that the bucket is deleted, but the error keeps persisting.

Error Message:

2023/09/19 15:16:56 Terraform apply | Error: BucketAlreadyExists: The requested bucket name is not available. The bucket namespace is shared by all users of the system. Please select a different name and try again.
2023/09/19 15:16:56 Terraform apply | status code: 409, request id: 2a864e0a-17ef-4882-a680-a7e9d3b71d5e, host id:
2023/09/19 15:16:56 Terraform apply |
2023/09/19 15:16:56 Terraform apply | with module.cos.ibm_cos_bucket.cos_bucket,
2023/09/19 15:16:56 Terraform apply | on modules/cos/cos_operations.tf line 21, in resource "ibm_cos_bucket" "cos_bucket":
2023/09/19 15:16:56 Terraform apply | 21: resource "ibm_cos_bucket" "cos_bucket" {
2023/09/19 15:16:56 Terraform apply |
2023/09/19 15:16:57 �[1m�[31mTerraform APPLY error: Terraform APPLY errorexit status 1�[39m�[0m
2023/09/19 15:16:57 �[1m�[31mCould not execute job: Error : Terraform APPLY errorexit status 1�[39m�[0m

We have pointed out the customer to refer below doc

https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-faq#faq-reuse-name

Snippet from doc bucket name re-use

"A bucket name can be reused as soon as 15 minutes after the contents of the bucket have been deleted and the bucket has been deleted. Then, the objects and bucket are irrevocably deleted and can not be restored.

If you do not first empty and then delete the bucket, and instead delete or schedule the Object Storage service instance for deletion, the bucket names will be held in reserve for a default period of seven (7) days until the account reclamation process is completed. Until the reclamation process is complete, it is possible to restore the instance, along with the buckets and objects. After reclamation is complete, all buckets and objects will be irrevocably deleted and can not be restored, although the bucket names will be made available for new buckets to reuse."

It will be helpful to the users to include the COS bucket name re-use info both in terraform provider registry documentation & README. So that user will be aware of how to re-use bucket name.

@github-actions github-actions bot added the service/Object Storage Issues related to Cloud Object Storage label Sep 25, 2023
@IBM-diksha
Copy link
Collaborator

IBM-diksha commented Oct 4, 2023

@umarali-nagoor Thank you so much for reaching out.
We have an internal ticket to track this and we will address this in our next releases.
Thank you.

IBM-Deeksha pushed a commit to IBM-Deeksha/terraform-provider-ibm that referenced this issue Jul 17, 2024
hkantare pushed a commit that referenced this issue Jul 17, 2024
* remove hardcoded values for private and direct cos config endpoint. Use defaults values when no env variables are set

* update code

* update code

* remove extra space

* update code

* update comment

* udpate documentation

* documentation update for issue #4819

* update doc

---------

Co-authored-by: Deeksha Sharma <[email protected]>
hkantare pushed a commit that referenced this issue Jul 18, 2024
* remove hardcoded values for private and direct cos config endpoint. Use defaults values when no env variables are set

* update code

* update code

* remove extra space

* update code

* update comment

* udpate documentation

* documentation update for issue #4819

* update doc

* read from endpoints file

---------

Co-authored-by: Deeksha Sharma <[email protected]>
@IBM-diksha
Copy link
Collaborator

The PR for this issue has been merged into the beta release for this month.
Version - v1.68.0-beta

@IBM-diksha
Copy link
Collaborator

Closing the ticket as the latest release has the documentation including the reuse information of the bucket after deletion.
Version - v1.68.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation enhancement service/Object Storage Issues related to Cloud Object Storage
Projects
None yet
Development

No branches or pull requests

2 participants