The Wire · Showcase
PACKER KUBEVIRT FIXES DEADLOCK THAT FROZE BUILDS
By RepoJournal · Filed · About HashiCorp
A critical fix in the KubeVirt plugin removes a deadlock that was leaving Packer builds stuck waiting for DataVolumes that would never bind.
The packer-plugin-kubevirt team shipped a fix that enables immediate binding for DataVolumes [1], resolving a deadlock where builds would hang indefinitely. The root cause: final image DataVolumes were created without requesting immediate binding, forcing Packer to wait for a consumer that never arrived. This is the kind of production blocker that deserves immediate attention if you're building container images on Kubernetes. In parallel, gRPC picked up a critical security patch [2] addressing HTTP/2 frame flooding attacks in the nomad-connect-examples repository, bumping the library from 1.82.0 to 1.82.1. Meanwhile, routine dependency maintenance continues across the ecosystem, with setup-go [3] migrating to ESM in net-rpc-msgpackrpc. The KubeVirt fix is your priority today.
One email a day. Unsubscribe in one click.
What actually shipped in HashiCorp, written up every day — commits, pull requests, releases, and security advisories.
One email a day. Unsubscribe in one click. Read a past issue →
Action items
- → Upgrade packer-plugin-kubevirt to pick up the deadlock fix if you build on KubeVirt hashicorp/packer-plugin-kubevirt [immediate]
- → Pull gRPC 1.82.1 into nomad-connect-examples to close the HTTP/2 frame flooding vulnerability hashicorp/nomad-connect-examples [plan]
- → Monitor setup-go 7.0.0 migration in your CI workflows for any ESM compatibility issues hashicorp/net-rpc-msgpackrpc [monitor]
References
- [1] fix: immediate binding for dv ↗ hashicorp/packer-plugin-kubevirt
- [2] build(deps): bump google.golang.org/grpc from 1.82.0 to 1.82.1 in /grpc-checks ↗ hashicorp/nomad-connect-examples
- [3] [chore] : Bump actions/setup-go from 6.5.0 to 7.0.0 in the actions group ↗ hashicorp/net-rpc-msgpackrpc