You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There seems to be enough issues in the past regarding disks that are attached and not being able to properly manage desired state: #7792 #12760 #12398
But if I run: gcloud compute disks delete DISKNAME
I get the following error from Google:
The following disks will be deleted:
- [DISKNAME] in [ZONE]
Do you want to continue (Y/n)? y
ERROR: (gcloud.compute.disks.delete) Could not fetch resource:
- The disk resource 'projects/-/zones/-/disks/DISKNAME' is already being used by 'projects/-/zones/-/instances/gke-0c4z....'
However, if I comment out the disk configuration in terraform and run apply,
Terraform will perform the following actions:
- module.-.module.-.google_compute_disk.disk
....
Apply complete! Resources: 0 added, 0 changed, 1 destroyed.
This then leaves everything that was attached to it in a strange state of not being able to connect.
My expected behaviour is to see the same error message that the gcloud command outputs.
The text was updated successfully, but these errors were encountered:
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
ghost
locked and limited conversation to collaborators
Apr 2, 2020
This issue was closed.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
There seems to be enough issues in the past regarding disks that are attached and not being able to properly manage desired state:
#7792
#12760
#12398
But if I run:
gcloud compute disks delete DISKNAME
I get the following error from Google:
However, if I comment out the disk configuration in terraform and run
apply
,Terraform will perform the following actions: - module.-.module.-.google_compute_disk.disk .... Apply complete! Resources: 0 added, 0 changed, 1 destroyed.
This then leaves everything that was attached to it in a strange state of not being able to connect.
My expected behaviour is to see the same error message that the
gcloud
command outputs.The text was updated successfully, but these errors were encountered: