docs(skill): default ci-repro VM boot disk to 100GB#12964
Open
electricjesus wants to merge 1 commit into
Open
Conversation
A repro VM builds FV prereqs locally (unlike CI VMs, which get prebuilt artifacts pushed to them), and the build overflows a small boot disk with 'no space left on device'. Hit in practice while reproducing a Felix FV flake on ubuntu-2510.
electricjesus
added
docs-not-required
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the ci-reproduce-on-gcp-vm skill documentation to use a larger default GCP VM boot disk size for reproducing CI failures locally, avoiding no space left on device during make fv prerequisite builds.
Changes:
- Increase the example
gcloud compute instances create--boot-disk-sizefrom20Gto100GB. - Clarify that CI’s default disk size is 20GB, but CI VMs receive prebuilt artifacts whereas repro VMs build locally and need more space.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The ci-reproduce-on-gcp-vm skill creates its VM with a 20G boot disk and says that matches CI defaults. That size works in CI because Semaphore pushes prebuilt images and binaries to the test VMs, but a repro VM runs the
make fvprereq builds itself, and the go-build image plus the felix and calico image builds plus the Go build cache overflow 20G withno space left on devicebefore the first test runs. Hit this in practice while reproducing a Felix FV flake on ubuntu-2510; had to live-resize the disk and rerun.Default to 100GB instead (and use the GB suffix the CI scripts use). A repro VM lives a few hours, so the price difference between the two sizes is noise.
Release note: