Skip to content

[Backport release-1.4] fix(objectstorage-controller): propagate Bucket readiness to BucketClaim - #2828

Merged
myasnikovdaniil merged 1 commit into
release-1.4from
backport-2792-to-release-1.4
Jun 5, 2026
Merged

myasnikovdaniil merged 1 commit into
release-1.4from
backport-2792-to-release-1.4

Conversation

@github-actions

@github-actions github-actions Bot commented Jun 5, 2026

Copy link
Copy Markdown

Description

Backport of #2792 to release-1.4.

The vendored COSI controller (v0.2.2) sets only BucketClaim.status.bucketName
in the dynamic-provisioning path and hardcodes bucketReady=false, never
re-reading the Bucket afterwards. The controller does not watch Buckets, so the
readiness transition the sidecar performs (false->true) is never reflected on
the BucketClaim: bucketReady stays false forever and BucketAccess is never
granted, leaving provisioned buckets without credentials.

Re-read the live Bucket after create and propagate its readiness, so the
periodic resync converges the BucketClaim to ready. This matches the behavior
the rewritten upstream controller already has on its main branch.

Assisted-By: Claude <[email protected]>
Signed-off-by: Aleksei Sviridkin <[email protected]>
(cherry picked from commit ed20a43)
@dosubot dosubot Bot added kind/backport Categorizes issue or PR as requiring a backport to the current release line kind/bug Categorizes issue or PR as related to a bug labels Jun 5, 2026
@myasnikovdaniil
myasnikovdaniil merged commit 05eeb09 into release-1.4 Jun 5, 2026
4 of 5 checks passed
@myasnikovdaniil
myasnikovdaniil deleted the backport-2792-to-release-1.4 branch June 5, 2026 12:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

kind/backport Categorizes issue or PR as requiring a backport to the current release line kind/bug Categorizes issue or PR as related to a bug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants