-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
CI: External workloads (ci-external-workloads) installation-and-connectivity: Create GCP VM failed #17063
Comments
xinyuannn
added
area/CI
Continuous Integration testing issue or flake
ci/flake
This is a known failure that occurs in the tree. Please investigate me!
labels
Aug 5, 2021
This is cilium/cilium-cli#445 (comment). |
nbusseneau
added a commit
that referenced
this issue
Aug 6, 2021
Fixes an issue where the GCP VM fails to create: ``` Run gcloud compute instances create cilium-cilium-cli-1046557892-vm \ WARNING: You have selected a disk size of under [200GB]. This may result in poor I/O performance. For more information, see: https://developers.google.com/compute/docs/disks#performance. ERROR: (gcloud.compute.instances.create) Could not fetch resource: - The resource 'projects/***/regions/us-west2/subnetworks/default' is not ready ``` From GCP documentation, this comes from simultaneous resource operations (https://cloud.google.com/compute/docs/troubleshooting/troubleshooting-vm-creation) however we have no control over that. Their only recommendation is to add retries. Considering it's an infrastructure issue and it also is easily contained to the GCP VM creation step, this is acceptable. Picked up from cilium/cilium-cli#463. Fixes: #17063 Signed-off-by: Nicolas Busseneau <nicolas@isovalent.com>
aanm
pushed a commit
that referenced
this issue
Aug 7, 2021
Fixes an issue where the GCP VM fails to create: ``` Run gcloud compute instances create cilium-cilium-cli-1046557892-vm \ WARNING: You have selected a disk size of under [200GB]. This may result in poor I/O performance. For more information, see: https://developers.google.com/compute/docs/disks#performance. ERROR: (gcloud.compute.instances.create) Could not fetch resource: - The resource 'projects/***/regions/us-west2/subnetworks/default' is not ready ``` From GCP documentation, this comes from simultaneous resource operations (https://cloud.google.com/compute/docs/troubleshooting/troubleshooting-vm-creation) however we have no control over that. Their only recommendation is to add retries. Considering it's an infrastructure issue and it also is easily contained to the GCP VM creation step, this is acceptable. Picked up from cilium/cilium-cli#463. Fixes: #17063 Signed-off-by: Nicolas Busseneau <nicolas@isovalent.com>
krishgobinath
pushed a commit
to krishgobinath/cilium
that referenced
this issue
Oct 20, 2021
Fixes an issue where the GCP VM fails to create: ``` Run gcloud compute instances create cilium-cilium-cli-1046557892-vm \ WARNING: You have selected a disk size of under [200GB]. This may result in poor I/O performance. For more information, see: https://developers.google.com/compute/docs/disks#performance. ERROR: (gcloud.compute.instances.create) Could not fetch resource: - The resource 'projects/***/regions/us-west2/subnetworks/default' is not ready ``` From GCP documentation, this comes from simultaneous resource operations (https://cloud.google.com/compute/docs/troubleshooting/troubleshooting-vm-creation) however we have no control over that. Their only recommendation is to add retries. Considering it's an infrastructure issue and it also is easily contained to the GCP VM creation step, this is acceptable. Picked up from cilium/cilium-cli#463. Fixes: cilium#17063 Signed-off-by: Nicolas Busseneau <nicolas@isovalent.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
CI failure
Stacktrace:
There is no sysdump generated.
https://github.com/cilium/cilium/actions/runs/1103142363
The text was updated successfully, but these errors were encountered: