ceph / ceph/ceph-cosi

objectstorage-sidecar latest image is incompatible with ceph-cosi:v0.1.2

Open
#38 4 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
56
Forks
20
PR merge metrics
No merged PRs in 30d

Description

Context : https://rook-io.slack.com/archives/C741SA742/p1739518336186929

I tried updating the sidecar image to
```
gcr.io/k8s-staging-sig-storage/objectstorage-sidecar:v20250117-a29e5f6
registry.k8s.io/sig-storage/objectstorage-sidecar:v0.2.1
```

and both are getting stuck when attempting to make the connection to the socket that is created by [quay.io/ceph/cosi:v0.1.2](http://quay.io/ceph/cosi:v0.1.2)
only the image [gcr.io/k8s-staging-sig-storage/objectstorage-sidecar:v20240513-v0.1.0-35-gefb3255](http://gcr.io/k8s-staging-sig-storage/objectstorage-sidecar:v20240513-v0.1.0-35-gefb3255) works as the sidecar.

Both images were getting stuck after printing
```
I0214 07:27:35.210080 1 cmd.go:79] "Attempting connection to driver" address="unix:///var/lib/cosi/cosi.sock"
```

Contributor guide

No contributing guide indexed for this repository

Research direction

Start at cmd.go:79 and reproduce the socket connection using ceph-cosi:v0.1.2 with each listed objectstorage-sidecar image. Compare the connection behavior and logs; done means a sidecar pairing connects to /var/lib/cosi/cosi.sock instead of hanging.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
backend, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.