- Issues
- #162
S3 first deploy fails creating missing deployment pointer on MinIO
ajoslin opened ·
celld v0.2.0, v0.2.1, and v0.3.0 fail their first deploy against MinIO when deploy/<script>/current.json is absent. The immutable bundle and manifest upload, then PutMode::Create returns NoSuchKey before creating the pointer. Reproduced with MinIO RELEASE.2025-09-06T17-38-46Z and RELEASE.2025-09-07T16-13-09Z, including root credentials. Error: conditional write .../deploy/<script>/current.json may have committed; caused by Object ... not found / NoSuchKey. Both pointer objects remain absent after failure. Suspected object_store 0.11.2 S3 conditional-create behavior. Expected: first conditional create succeeds atomically; subsequent deploys use CAS update.
- BA
Thanks, I'll look into it on Monday
bartlomiejuassigned bartlomieju3 months ago on GitHub
- BA
This looks like a is a MinIO regression, not celld: [minio/minio#21550](https://github.com/minio/minio/issues/21550) (RELEASE.2025-09-06T17-38-46Z) made PUT + If-None-Match: * on a missing key return NoSuchKey; [minio/minio#21567](https://github.com/minio/minio/issues/21567) fixed it in RELEASE.2025-09-07T16-13-09Z. I reproduced your exact error against a 09-06 build and verified the first deploy succeeds against the published 09-07 image (and later releases). Please re-check which MinIO binary your 09-07 test actually ran (`mc admin info` reports the running version).
- AJ
Confirmed thanks
Siddhj2206referenced this in Verify celld single-node durability before committing the substrate #2last month on GitHub