Skip to content

chore(seaweedfs): bump seaweedfs-cosi-driver to v0.3.1 - #2791

Merged
Aleksei Sviridkin (lexfrei) merged 1 commit into
mainfrom
chore/seaweedfs-cosi-driver-v0.3.1
Jun 5, 2026
Merged

chore(seaweedfs): bump seaweedfs-cosi-driver to v0.3.1#2791
Aleksei Sviridkin (lexfrei) merged 1 commit into
mainfrom
chore/seaweedfs-cosi-driver-v0.3.1

Conversation

@lexfrei

@lexfrei Aleksei Sviridkin (lexfrei) commented Jun 2, 2026

Copy link
Copy Markdown
Contributor

What this PR does

Bumps the seaweedfs-cosi-driver image from v0.3.0 to v0.3.1.

v0.3.1 ships 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 an emptyDir that survives container restarts, the next start failed with bind: address already in use and the objectstorage-provisioner wedged in CrashLoopBackOff. While it was down, BucketClaim reconciliation stopped and buckets were never provisioned — the COSI Bucket could even report bucketReady: true while 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

fix(seaweedfs): bump seaweedfs-cosi-driver to v0.3.1, which self-heals the object storage COSI provisioner from a CrashLoopBackOff caused by a stale unix socket

Summary by CodeRabbit

  • Chores
    • Updated SeaweedFS cosi driver container image to a newer version.

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>
@github-actions github-actions Bot added area/storage Issues or PRs related to storage (linstor, seaweedfs, bucket, velero, harbor) kind/cleanup Categorizes issue or PR as related to cleanup of code, process, or technical debt size/XS This PR changes 0-9 lines, ignoring generated files labels Jun 2, 2026
@dosubot dosubot Bot added area/extra Issues or PRs related to tenant-specific modules (packages/extra/) backport Should change be backported on previous release kind/bug Categorizes issue or PR as related to a bug labels Jun 2, 2026
@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, 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

  • Version Upgrade: Updated the seaweedfs-cosi-driver image from v0.3.0 to v0.3.1.
  • Bug Fix: Implemented a fix for stale unix sockets that previously caused CrashLoopBackOff errors following non-graceful container restarts.
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 Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment Gemini (@gemini-code-assist) Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@coderabbitai

coderabbitai Bot commented Jun 2, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 469c3ad1-da5a-480f-89e7-58a2ecd578fd

📥 Commits

Reviewing files that changed from the base of the PR and between 26da871 and 7857282.

📒 Files selected for processing (1)
  • packages/extra/seaweedfs/images/seaweedfs-cosi-driver.tag

📝 Walkthrough

Walkthrough

This PR updates the SeaweedFS COSI driver container image tag from v0.3.0 to v0.3.1 in the image reference file. The change applies a single version bump to the container image specification.

Changes

Image Tag Update

Layer / File(s) Summary
Image tag version bump
packages/extra/seaweedfs/images/seaweedfs-cosi-driver.tag
Container image tag for SeaweedFS COSI driver is updated from v0.3.0 to v0.3.1.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A version bump, so small and neat,
From point-three-oh to one—a treat!
The COSI driver takes its flight,
With v-point-three-one shining bright! ✨

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely summarizes the main change: bumping the seaweedfs-cosi-driver version from v0.3.0 to v0.3.1, which matches the single file change in the PR.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/seaweedfs-cosi-driver-v0.3.1

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@kvaps Andrei Kvapil (kvaps) left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@lexfrei
Aleksei Sviridkin (lexfrei) merged commit 083811a into main Jun 5, 2026
17 of 18 checks passed
@lexfrei
Aleksei Sviridkin (lexfrei) deleted the chore/seaweedfs-cosi-driver-v0.3.1 branch June 5, 2026 08:09
@github-actions

github-actions Bot commented Jun 5, 2026

Copy link
Copy Markdown

Successfully created backport PR for release-1.4:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/extra Issues or PRs related to tenant-specific modules (packages/extra/) area/storage Issues or PRs related to storage (linstor, seaweedfs, bucket, velero, harbor) backport Should change be backported on previous release kind/bug Categorizes issue or PR as related to a bug kind/cleanup Categorizes issue or PR as related to cleanup of code, process, or technical debt size/XS This PR changes 0-9 lines, ignoring generated files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants