chore(seaweedfs): bump seaweedfs-cosi-driver to v0.3.1 - #2791
Conversation
v0.3.1 ships the stale-socket self-heal: the driver removes a leftover COSI unix socket before binding, so the objectstorage provisioner recovers from CrashLoopBackOff after a non-graceful exit (SIGKILL / OOM / panic) instead of wedging on "bind: address already in use". Assisted-By: Claude <noreply@anthropic.com> Signed-off-by: Aleksei Sviridkin <f@lex.la>
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request updates the seaweedfs-cosi-driver to version v0.3.1 to resolve a critical issue where leftover unix sockets prevented the provisioner from binding correctly upon restart. This ensures the object storage provisioner can self-heal after unexpected exits, maintaining continuous bucket reconciliation. Highlights
New Features🧠 You can now enable Memory (public preview) to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on Gemini (@gemini-code-assist) comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request updates the seaweedfs-cosi-driver image tag from v0.3.0 to v0.3.1. There are no review comments, and I have no feedback to provide.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThis PR updates the SeaweedFS COSI driver container image tag from ChangesImage Tag Update
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Andrei Kvapil (kvaps)
left a comment
There was a problem hiding this comment.
Verified the bump end-to-end: v0.3.1 upstream release exists and its only change vs v0.3.0 is the stale-socket self-heal fix (seaweedfs/seaweedfs-cosi-driver#8); the ghcr image is published multi-arch (linux/amd64 + linux/arm64); and the .tag file is the single consumption point ($.Files.Get in cosi-deployment.yaml), so the bump is complete.
|
Successfully created backport PR for |
What this PR does
Bumps the
seaweedfs-cosi-driverimage fromv0.3.0tov0.3.1.v0.3.1ships the stale-socket self-heal fix. After a non-graceful exit (SIGKILL / OOM / panic) Go does not unlink the COSI unix socket, and because it lives on anemptyDirthat survives container restarts, the next start failed withbind: address already in useand theobjectstorage-provisionerwedged inCrashLoopBackOff. While it was down,BucketClaimreconciliation stopped and buckets were never provisioned — the COSIBucketcould even reportbucketReady: truewhile no bucket existed. This is the CrashLoopBackOff reported in #2429.The driver now removes a leftover socket before binding (only when it exists, is a socket, and has no live listener), so the provisioner self-heals on restart.
Upstream: seaweedfs/seaweedfs-cosi-driver#8 (merged), released in v0.3.1. Points at the upstream published multi-arch image (amd64 + arm64) — no vendoring needed.
Release note
Summary by CodeRabbit