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

Decomission old AWI-CIROH infrastructure #4483

Closed
3 of 4 tasks
yuvipanda opened this issue Jul 24, 2024 · 6 comments · Fixed by #4517
Closed
3 of 4 tasks

Decomission old AWI-CIROH infrastructure #4483

yuvipanda opened this issue Jul 24, 2024 · 6 comments · Fixed by #4517
Assignees

Comments

@yuvipanda
Copy link
Member

yuvipanda commented Jul 24, 2024

#4238 is complete. We wait until Monday, July 29 and see if there are any user reported issues. If not, we decomission the old infrastructure.

  • We wait until Monday, July 29
  • Decomission the awi-ciroh terraform workspace. May need a git checkout from before Remove AWI-CIROH original cluster from CI/CD #4444 was merged
  • Look at the awi-ciroh GCP project, make sure it's completely empty and all resources (including ones that were manually created for the transfer) are deleted
  • Rename the awi-ciroh-2 terraform workspace to awi-ciroh
@sgibson91
Copy link
Member

sgibson91 commented Jul 25, 2024

Shit, I just remembered we were supposed to wait until Monday.

I got blocked on the AWS stuff though which is why I switched tack.


For future reference, GitHub recognises and renders Obsidian flavoured markdown. So the following:

> [!warning]
> Wait until Monday 29th July

renders as:

Warning

Wait until Monday 29th July

@sgibson91
Copy link
Member

sgibson91 commented Jul 25, 2024

This is blocked now also anyway

 Error: Error trying to delete bucket awi-ciroh-scratch containing objects without `force_destroy` set to true
│ 
│ 
╵
╷
│ Error: Error trying to delete bucket awi-ciroh-persistent containing objects without `force_destroy` set to true
│ 
│ 
╵
╷
│ Error: Cannot destroy cluster because deletion_protection is set to true. Set it to false to proceed with cluster deletion.
│ 
│ 
╵
╷
│ Error: Error trying to delete bucket awi-ciroh-persistent-staging containing objects without `force_destroy` set to true
│ 

I tried adding the relevant variables in the appropriate places in our code, but unless these variables are already in terraform state, it has no effect.

https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/container_cluster#:~:text=deletion_protection%20%2D%20(Optional)%20Whether%20or,delete%20the%20cluster%20will%20fail.

@sgibson91
Copy link
Member

Ok, after allowing my brain to stew in other ridiculous problems, I think my mistake here was trying to do a tf apply -destroy straight away instead of applying the additions first.

@sgibson91
Copy link
Member

I used the Asset Inventory to check which resources where left over: https://console.cloud.google.com/iam-admin/asset-inventory/resources A lot of what's left in here are default resources (I think, I'm looking at the LogBuckets there) and enabled APIs.

I deleted two object storage buckets, three VM instances, and a BigQuery service account that weren't cleaned up by terraform.

@sgibson91
Copy link
Member

I followed these steps to rename the workspace https://discuss.hashicorp.com/t/how-to-change-the-name-of-a-workspace/24010/2

@yuvipanda
Copy link
Member Author

Thank you, @sgibson91!

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

Successfully merging a pull request may close this issue.

2 participants