[kubernetes] Fix dead-lock while reattaching a KubeVirt-CSI volume - #1135
Conversation
|
Warning Rate limit exceededAndrei Kvapil (@kvaps) has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 16 minutes and 49 seconds before requesting another review. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📒 Files selected for processing (1)
WalkthroughThe kubevirt-csi-driver Dockerfile was updated to check out a new Git commit and apply local patch files during the build. The controller service was enhanced with new VM-specific volume presence checks to optimize attach/detach operations by skipping redundant calls. Corresponding tests and mocks were added or updated. Changes
Poem
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Actionable comments posted: 1
🔭 Outside diff range comments (1)
packages/apps/kubernetes/images/kubevirt-csi-driver/Dockerfile (1)
17-22: Metadata drift – LABEL still points to the upstream repo
multi.GIT_URLadvertiseshttps://github.com/kubevirt/csi-driver.git, which no longer matches the actual cloned source.
This causes confusion and breaks provenance tracking.-ARG git_url=https://github.com/kubevirt/csi-driver.git +ARG git_url=https://github.com/kvaps/csi-driver.gitRemember to propagate the same ARG (or the new
repo_url) into the LABEL to keep the image metadata truthful.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
packages/apps/kubernetes/images/kubevirt-csi-driver/Dockerfile(1 hunks)
🧰 Additional context used
🪛 GitHub Actions: Pull Request
packages/apps/kubernetes/images/kubevirt-csi-driver/Dockerfile
[error] 4-6: Docker build failed: git clone and checkout failed with 'fatal: reference is not a tree: 35836e0c8b68d9916d29a838ea60cdd3fc6199cf'. Command exited with code 128.
🔇 Additional comments (1)
packages/apps/kubernetes/images/kubevirt-csi-driver/Dockerfile (1)
4-6: Security/provenance consideration – pulling from a personal forkSwitching from the official upstream to a fork introduces supply-chain risk. Make sure:
- The chosen commit is reviewed & signed.
- SBOM / provenance attestation is updated.
- Upstream is informed so the fix can be merged back, eliminating the need for the fork.
d583f82 to
0671559
Compare
Timofei Larkin (lllamnyp)
left a comment
There was a problem hiding this comment.
If it's good enough for upstream, it's good enough for us/
Signed-off-by: Andrei Kvapil <kvapss@gmail.com>
0671559 to
4c347cc
Compare
|
PR rebased, patch removed and now targets on upstream commit |
What this PR does
This pr imports upstream fix for volume reattaching procedure
Release note
Summary by CodeRabbit
New Features
Tests