-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[PVC] the prebuild workspace is unable to be up and running #13980
Comments
@jenting can you pause on this issue and its PRs? Let's wait to see if Google can remove the snapshot/volume limit. I ask because we may proceed and do PVC just for regular workspaces. cc: @sagor999 |
For prebuild workspaces, we'll use GCP image to backup prebuild workspace PVC. Ref to https://www.notion.so/gitpod/Next-steps-for-PVC-given-snapshot-volume-limits-593d5d804e734f459a8935208b57903b. |
PR both merged, waiting for the deployment, and closing it. |
Bug description
The prebuild workspace is unable to be up and running.
It's the limitation of the GCP regional disk. We can't create a new zonal persistent disk from the same snapshot in the same zone, more than once in 10 minutes. https://cloud.google.com/compute/docs/troubleshooting/troubleshooting-snapshots#creating_new_zonal_persistent_disks_from_snapshots
Steps to reproduce
Enable the projects prebuild PVC
https://gitpod.slack.com/archives/C02F19UUW6S/p1666105041014279
Workspace affected
No response
Expected behavior
The prebuild workspace should be up and running.
Example repository
No response
Anything else?
#7901
The text was updated successfully, but these errors were encountered: