Add CRR Cascaded capabilities by SylvainSenechal · Pull Request #6179 · scality/cloudserver

SylvainSenechal · 2026-05-29T18:00:35Z

Crr cascaded design : https://github.com/scality/citadel/pull/349

Related PRs :
Arsenal : scality/Arsenal#2628
CloudserverClient : scality/cloudserverclient#24
Backbeat : scality/backbeat#2747
S3utils : scality/s3utils#395

bert-e · 2026-05-29T18:00:39Z

Hello sylvainsenechal,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options

name	description	privileged	authored
`/after_pull_request`	Wait for the given pull request id to be merged before continuing with the current one.
`/bypass_author_approval`	Bypass the pull request author's approval	⭐
`/bypass_build_status`	Bypass the build and test status	⭐
`/bypass_commit_size`	Bypass the check on the size of the changeset `TBA`	⭐
`/bypass_incompatible_branch`	Bypass the check on the source branch prefix	⭐
`/bypass_jira_check`	Bypass the Jira issue check	⭐
`/bypass_peer_approval`	Bypass the pull request peers' approval	⭐
`/bypass_leader_approval`	Bypass the pull request leaders' approval	⭐
`/approve`	Instruct Bert-E that the author has approved the pull request.		✍️
`/create_pull_requests`	Allow the creation of integration pull requests.
`/create_integration_branches`	Allow the creation of integration branches.
`/no_octopus`	Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
`/unanimity`	Change review acceptance criteria from `one reviewer at least` to `all reviewers`
`/wait`	Instruct Bert-E not to run until further notice.

Available commands

name	description	privileged
`/help`	Print Bert-E's manual in the pull request.
`/status`	Print Bert-E's current status in the pull request `TBA`
`/clear`	Remove all comments from Bert-E from the history `TBA`
`/retry`	Re-start a fresh build `TBA`
`/build`	Re-start a fresh build `TBA`
`/force_reset`	Delete integration branches & pull requests, and restart merge process from the beginning.
`/reset`	Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

SylvainSenechal · 2026-05-29T18:03:07Z

+                bucketName: request.bucketName,
+                objectKey: request.objectKey,
+            });
+            return callback(errors.OperationAborted);


many 409 available in arsenal. we can pick this one, maybe some other ones, or create our own

claude · 2026-05-29T18:04:39Z

        "@hapi/joi": "^17.1.1",
        "@smithy/node-http-handler": "^3.0.0",
-        "arsenal": "git+https://github.com/scality/Arsenal#8.4.2",
+        "arsenal": "file:../Arsenal",


arsenal and @scality/cloudserverclient are pointing to local filesystem paths (file:../Arsenal, file:../cloudserverclient) instead of pinned git tags. This will break installs for anyone who does not have these directories locally, and CI will fail to resolve them.

Suggested change

"arsenal": "file:../Arsenal",

"arsenal": "git+https://github.com/scality/Arsenal#8.4.2",

— Claude Code

claude · 2026-05-29T18:04:46Z

    "devDependencies": {
        "@eslint/compat": "^1.2.2",
-        "@scality/cloudserverclient": "1.0.7",
+        "@scality/cloudserverclient": "file:../cloudserverclient",


Same issue: file:../cloudserverclient should be pinned to a published version or git tag.

— Claude Code

claude · 2026-05-29T18:04:55Z

+});
+
+describe('CRR cascade — putMetadata', () => {
+    it('second write with the same microVersionId returns loop-detected', async () => {


Test names using it() should start with should per project conventions.

— Claude Code

claude · 2026-05-29T18:05:03Z

+            }],
+        },
+    }));
+});


Missing after() hook to clean up the test buckets (TEST_BUCKET, TEST_BUCKET_CRR, DEST_BUCKET). Without cleanup, leftover buckets accumulate across test runs and can cause name collisions or resource leaks.

— Claude Code

bucket/keys names are randomized
I intentionnally didnt add any after to keep the test and file lighter.

Do we want to add after cleanup ?

claude · 2026-05-29T18:05:14Z

Dependency pinning: arsenal and @scality/cloudserverclient in package.json use file: paths pointing to local directories. These must be pinned to git tags or published versions before merge.
- arsenal on line 36: file:../Arsenal → should be a git tag (e.g. 8.4.2)
- @scality/cloudserverclient on line 68: file:../cloudserverclient → should be a versioned reference
Test naming: it() descriptions in tests/functional/backbeat/crrCascade.js should start with should per project conventions.
Test cleanup: No after() hook to delete the three buckets created in before(). Leftover buckets will accumulate across test runs.

Review by Claude Code

SylvainSenechal · 2026-05-29T18:09:19Z

all these worked locally, need to wait for the bumps now

SylvainSenechal · 2026-05-29T18:09:35Z

        "@hapi/joi": "^17.1.1",
        "@smithy/node-http-handler": "^3.0.0",
-        "arsenal": "git+https://github.com/scality/Arsenal#8.4.2",
+        "arsenal": "file:../Arsenal",


codecov · 2026-05-29T18:39:41Z

❌ 103 Tests Failed:

Tests completed	Failed	Passed	Skipped
3626	103	3523	0

View the top 3 failed test(s) by shortest run time

GET /_/backbeat/api/... should respond with 403 if the request is unauthenticated::backbeat routes backbeat authorization checks when api proxy is configured GET /_/backbeat/api/... should respond with 403 if the request is unauthenticated

Stack Traces | 0s run time

Expected values to be strictly equal:

undefined !== 403

GET /_/backbeat/api/... should respond with 503 on authenticated requests (API server down)::backbeat routes backbeat authorization checks when api proxy is configured GET /_/backbeat/api/... should respond with 503 on authenticated requests (API server down)

Stack Traces | 0s run time

Expected values to be strictly equal:

undefined !== 503

PUT data should respond with 403 Forbidden if backbeat user has wrong secret key::backbeat routes backbeat authorization checks PUT data should respond with 403 Forbidden if backbeat user has wrong secret key

Stack Traces | 0s run time

Expected values to be strictly equal:

undefined !== 403

PUT data should respond with 403 Forbidden if the account does not match the backbeat user::backbeat routes backbeat authorization checks PUT data should respond with 403 Forbidden if the account does not match the backbeat user

Stack Traces | 0s run time

Expected values to be strictly equal:

undefined !== 403

PUT data should respond with 403 Forbidden if wrong credentials are provided::backbeat routes backbeat authorization checks PUT data should respond with 403 Forbidden if wrong credentials are provided

Stack Traces | 0s run time

Expected values to be strictly equal:

undefined !== 403

should return 200 when x-amz-checksum-sha256 matches body::backbeat routes checksum validation putObject (multiplebackenddata) should return 200 when x-amz-checksum-sha256 matches body

Stack Traces | 0s run time

ifError got unwanted exception: connect ECONNREFUSED 127.0.0.1:8000

with key Pâtisserie=中文-español-English::backbeat routes backbeat PUT routes PUT data + metadata should create a new complete object with key Pâtisserie=中文-español-English

Stack Traces | 0s run time

ifError got unwanted exception: connect ECONNREFUSED 127.0.0.1:8000

with key notes/spring/1.txt::backbeat routes backbeat PUT routes PUT data + metadata should create a new complete object with key notes/spring/1.txt

Stack Traces | 0s run time

ifError got unwanted exception: connect ECONNREFUSED 127.0.0.1:8000

with key notes/spring/2.txt::backbeat routes backbeat PUT routes PUT data + metadata should create a new complete object with key notes/spring/2.txt

Stack Traces | 0s run time

ifError got unwanted exception: connect ECONNREFUSED 127.0.0.1:8000

with key notes/summer/august/1.txt::backbeat routes backbeat PUT routes PUT data + metadata should create a new complete object with key notes/summer/august/1.txt

Stack Traces | 0s run time

ifError got unwanted exception: connect ECONNREFUSED 127.0.0.1:8000

with key notes/year.txt::backbeat routes backbeat PUT routes PUT data + metadata should create a new complete object with key notes/year.txt

Stack Traces | 0s run time

ifError got unwanted exception: connect ECONNREFUSED 127.0.0.1:8000

with key notes/yore.rs::backbeat routes backbeat PUT routes PUT data + metadata should create a new complete object with key notes/yore.rs

Stack Traces | 0s run time

ifError got unwanted exception: connect ECONNREFUSED 127.0.0.1:8000

with key 䆩鈁櫨㟔罳/䆩鈁櫨㟔罳/%42/mykey::backbeat routes backbeat PUT routes PUT data + metadata should create a new complete object with key 䆩鈁櫨㟔罳/䆩鈁櫨㟔罳/%42/mykey

Stack Traces | 0s run time

ifError got unwanted exception: connect ECONNREFUSED 127.0.0.1:8000

"after all" hook in "backbeat routes"::backbeat routes "after all" hook in "backbeat routes"

Stack Traces | 0.001s run time

connect ECONNREFUSED 127.0.0.1:8000

"before all" hook for "should return empty list of current versions if bucket is empty"::listLifecycleCurrents with bucket versioning Disabled "before all" hook for "should return empty list of current versions if bucket is empty"

Stack Traces | 0.001s run time

connect ECONNREFUSED 127.0.0.1:8000

"before all" hook for "should return list of current versions when bucket has a null current version"::listLifecycle with null current version after versioning suspended "before all" hook for "should return list of current versions when bucket has a null current version"

Stack Traces | 0.001s run time

connect ECONNREFUSED 127.0.0.1:8000

"before all" hook for "should return no current object if current version is a delete marker"::listLifecycle with current delete marker version "before all" hook for "should return no current object if current version is a delete marker"

Stack Traces | 0.001s run time

connect ECONNREFUSED 127.0.0.1:8000

"before all" hook for "should return truncated lists - part 1"::listLifecycleCurrents with bucket versioning enabled and delete object "before all" hook for "should return truncated lists - part 1"

Stack Traces | 0.001s run time

connect ECONNREFUSED 127.0.0.1:8000

"before each" hook for "should return metadata blob for a versionId"::backbeat routes GET Metadata route "before each" hook for "should return metadata blob for a versionId"

Stack Traces | 0.001s run time

connect ECONNREFUSED 127.0.0.1:8000

GET /_/backbeat/api/... should respond with 405 if the request is unauthenticated::backbeat routes backbeat authorization checks when api proxy is NOT configured GET /_/backbeat/api/... should respond with 405 if the request is unauthenticated

Stack Traces | 0.001s run time

Expected values to be strictly equal:

undefined !== 405

GET /_/backbeat/api/... should respond with 405 on authenticated requests (API server down)::backbeat routes backbeat authorization checks when api proxy is NOT configured GET /_/backbeat/api/... should respond with 405 on authenticated requests (API server down)

Stack Traces | 0.001s run time

Expected values to be strictly equal:

undefined !== 405

PUT data should respond with 403 Forbidden if no credentials are provided::backbeat routes backbeat authorization checks PUT data should respond with 403 Forbidden if no credentials are provided

Stack Traces | 0.001s run time

Expected values to be strictly equal:

undefined !== 403

PUT metadata should respond with 403 Forbidden if backbeat user has wrong secret key::backbeat routes backbeat authorization checks PUT metadata should respond with 403 Forbidden if backbeat user has wrong secret key

Stack Traces | 0.001s run time

Expected values to be strictly equal:

undefined !== 403

PUT metadata should respond with 403 Forbidden if no credentials are provided::backbeat routes backbeat authorization checks PUT metadata should respond with 403 Forbidden if no credentials are provided

Stack Traces | 0.001s run time

Expected values to be strictly equal:

undefined !== 403

PUT metadata should respond with 403 Forbidden if the account does not match the backbeat user::backbeat routes backbeat authorization checks PUT metadata should respond with 403 Forbidden if the account does not match the backbeat user

Stack Traces | 0.001s run time

Expected values to be strictly equal:

undefined !== 403

PUT metadata should respond with 403 Forbidden if wrong credentials are provided::backbeat routes backbeat authorization checks PUT metadata should respond with 403 Forbidden if wrong credentials are provided

Stack Traces | 0.001s run time

Expected values to be strictly equal:

undefined !== 403

should PUT tags for a non-versioned bucket (awslocation)::backbeat routes backbeat PUT routes should PUT tags for a non-versioned bucket (awslocation)

Stack Traces | 0.001s run time

ifError got unwanted exception: connect ECONNREFUSED 127.0.0.1:8000

should create a new version when no versionId is passed in query string::backbeat routes backbeat PUT routes should create a new version when no versionId is passed in query string

Stack Traces | 0.001s run time

ifError got unwanted exception: connect ECONNREFUSED 127.0.0.1:8000

should not remove data locations on replayed metadata PUT::backbeat routes backbeat PUT routes should not remove data locations on replayed metadata PUT

Stack Traces | 0.001s run time

ifError got unwanted exception: connect ECONNREFUSED 127.0.0.1:8000

should put tags if the source is AWS and tags are provided when initiating the multipart upload::backbeat routes backbeat multipart upload operations (external location) should put tags if the source is AWS and tags are provided when initiating the multipart upload

Stack Traces | 0.001s run time

connect ECONNREFUSED 127.0.0.1:8000

should put tags if the source is Azure and tags are provided when completing the multipart upload::backbeat routes backbeat multipart upload operations (external location) should put tags if the source is Azure and tags are provided when completing the multipart upload

Stack Traces | 0.001s run time

connect ECONNREFUSED 127.0.0.1:8000

should refuse PUT data if bucket is not versioned and x-scal-versioning-required is true::backbeat routes backbeat PUT routes should refuse PUT data if bucket is not versioned and x-scal-versioning-required is true

Stack Traces | 0.001s run time

Expected values to be strictly equal:
+ actual - expected

+ 'ECONNREFUSED'
- 'InvalidBucketState'

should refuse PUT data if no x-scal-canonical-id header is provided::backbeat routes backbeat PUT routes should refuse PUT data if no x-scal-canonical-id header is provided

Stack Traces | 0.001s run time

Expected values to be strictly equal:
+ actual - expected

+ 'ECONNREFUSED'
- 'BadRequest'

should refuse PUT in metadata-only mode if object does not exist::backbeat routes backbeat PUT routes should refuse PUT in metadata-only mode if object does not exist

Stack Traces | 0.001s run time

Expected values to be strictly equal:

undefined !== 404

should refuse PUT metadata if bucket is not versioned and x-scal-versioning-required is true::backbeat routes backbeat PUT routes should refuse PUT metadata if bucket is not versioned and x-scal-versioning-required is true

Stack Traces | 0.001s run time

Expected values to be strictly equal:
+ actual - expected

+ 'ECONNREFUSED'
- 'InvalidBucketState'

should refuse PUT metadata if bucket is version suspended and x-scal-versioning-required is true::backbeat routes backbeat PUT routes should refuse PUT metadata if bucket is version suspended and x-scal-versioning-required is true

Stack Traces | 0.001s run time

Expected values to be strictly equal:
+ actual - expected

+ 'ECONNREFUSED'
- 'InvalidBucketState'

should remove old object data locations if version is overwritten with empty contents::backbeat routes backbeat PUT routes should remove old object data locations if version is overwritten with empty contents

Stack Traces | 0.001s run time

ifError got unwanted exception: connect ECONNREFUSED 127.0.0.1:8000

should remove old object data locations if version is overwritten with same contents::backbeat routes backbeat PUT routes should remove old object data locations if version is overwritten with same contents

Stack Traces | 0.001s run time

ifError got unwanted exception: connect ECONNREFUSED 127.0.0.1:8000

should return 200 when x-amz-checksum-sha256 matches body::backbeat routes checksum validation putData should return 200 when x-amz-checksum-sha256 matches body

Stack Traces | 0.001s run time

ifError got unwanted exception: connect ECONNREFUSED 127.0.0.1:8000

should return 400 BadDigest when x-amz-checksum-sha256 does not match body::backbeat routes checksum validation putData should return 400 BadDigest when x-amz-checksum-sha256 does not match body

Stack Traces | 0.001s run time

Expected values to be strictly equal:

undefined !== 400

should return 400 BadDigest when x-amz-checksum-sha256 does not match body::backbeat routes checksum validation putObject (multiplebackenddata) should return 400 BadDigest when x-amz-checksum-sha256 does not match body

Stack Traces | 0.001s run time

Expected values to be strictly equal:

undefined !== 400

should skip batch delete of a non-existent location::backbeat routes Batch Delete Route should skip batch delete of a non-existent location

Stack Traces | 0.001s run time

connect ECONNREFUSED 127.0.0.1:8000

should skip batch delete of empty location array::backbeat routes Batch Delete Route should skip batch delete of empty location array

Stack Traces | 0.001s run time

connect ECONNREFUSED 127.0.0.1:8000

should throw VersionIdCollisionException with MicroVersionId when versionId matches current master::CRR cascade : putData should throw VersionIdCollisionException with MicroVersionId when versionId matches current master

Stack Traces | 0.001s run time

connect ECONNREFUSED 127.0.0.1:8000

should write data normally when VersionId does not match the current master::CRR cascade : putData should write data normally when VersionId does not match the current master

Stack Traces | 0.001s run time

connect ECONNREFUSED 127.0.0.1:8000

with UTF8 key::backbeat routes backbeat PUT routes PUT data + metadata should create a new complete object with UTF8 key

Stack Traces | 0.001s run time

ifError got unwanted exception: connect ECONNREFUSED 127.0.0.1:8000

with ascii test key::backbeat routes backbeat PUT routes PUT data + metadata should create a new complete object with ascii test key

Stack Traces | 0.001s run time

ifError got unwanted exception: connect ECONNREFUSED 127.0.0.1:8000

with encryption configuration and legacy API v1::backbeat routes backbeat PUT routes PUT data + metadata should create a new complete object with encryption configuration and legacy API v1

Stack Traces | 0.001s run time

ifError got unwanted exception: connect ECONNREFUSED 127.0.0.1:8000

with encryption configuration::backbeat routes backbeat PUT routes PUT data + metadata should create a new complete object with encryption configuration

Stack Traces | 0.001s run time

ifError got unwanted exception: connect ECONNREFUSED 127.0.0.1:8000

with key notes/spring/march/1.txt::backbeat routes backbeat PUT routes PUT data + metadata should create a new complete object with key notes/spring/march/1.txt

Stack Traces | 0.001s run time

ifError got unwanted exception: connect ECONNREFUSED 127.0.0.1:8000

with key notes/summer/1.txt::backbeat routes backbeat PUT routes PUT data + metadata should create a new complete object with key notes/summer/1.txt

Stack Traces | 0.001s run time

ifError got unwanted exception: connect ECONNREFUSED 127.0.0.1:8000

with key notes/summer/2.txt::backbeat routes backbeat PUT routes PUT data + metadata should create a new complete object with key notes/summer/2.txt

Stack Traces | 0.001s run time

ifError got unwanted exception: connect ECONNREFUSED 127.0.0.1:8000

with key notes/zaphod/Beeblebrox.txt::backbeat routes backbeat PUT routes PUT data + metadata should create a new complete object with key notes/zaphod/Beeblebrox.txt

Stack Traces | 0.001s run time

ifError got unwanted exception: connect ECONNREFUSED 127.0.0.1:8000

with legacy API v1::backbeat routes backbeat PUT routes PUT data + metadata should create a new complete object with legacy API v1

Stack Traces | 0.001s run time

ifError got unwanted exception: connect ECONNREFUSED 127.0.0.1:8000

with percents and spaces encoded as '+' in key::backbeat routes backbeat PUT routes PUT data + metadata should create a new complete object with percents and spaces encoded as '+' in key

Stack Traces | 0.001s run time

ifError got unwanted exception: connect ECONNREFUSED 127.0.0.1:8000

"after each" hook for "should update metadata of a current null version"::backbeat routes null version "after each" hook for "should update metadata of a current null version"

Stack Traces | 0.002s run time

socket hang up

"before all" hook for "should return empty list of current versions if bucket is empty"::listLifecycleCurrents with bucket versioning Enabled "before all" hook for "should return empty list of current versions if bucket is empty"

Stack Traces | 0.002s run time

connect ECONNREFUSED 127.0.0.1:8000

"before all" hook for "should return empty list of noncurrent versions if bucket is empty"::listLifecycleNonCurrents "before all" hook for "should return empty list of noncurrent versions if bucket is empty"

Stack Traces | 0.002s run time

connect ECONNREFUSED 127.0.0.1:8000

"before all" hook for "should return the current version"::listLifecycle with non-current delete marker "before all" hook for "should return the current version"

Stack Traces | 0.002s run time

connect ECONNREFUSED 127.0.0.1:8000

"before all" hook for "should return the null noncurrent versions"::listLifecycle if null version "before all" hook for "should return the null noncurrent versions"

Stack Traces | 0.002s run time

connect ECONNREFUSED 127.0.0.1:8000

"before all" hook for "should return truncated lists - part 1"::listLifecycleCurrents with bucket versioning enabled and maxKeys "before all" hook for "should return truncated lists - part 1"

Stack Traces | 0.002s run time

connect ECONNREFUSED 127.0.0.1:8000

should batch delete a local location::backbeat routes Batch Delete Route should batch delete a local location

Stack Traces | 0.002s run time

connect ECONNREFUSED 127.0.0.1:8000

should refuse PUT data if bucket is version suspended and x-scal-versioning-required is true::backbeat routes backbeat PUT routes should refuse PUT data if bucket is version suspended and x-scal-versioning-required is true

Stack Traces | 0.002s run time

Expected values to be strictly equal:
+ actual - expected

+ 'ECONNREFUSED'
- 'InvalidBucketState'

should set a microVersionId on a regular S3 PutObject::CRR cascade : S3 PUT sets microVersionId should set a microVersionId on a regular S3 PutObject

Stack Traces | 0.002s run time

connect ECONNREFUSED 127.0.0.1:8000

"before all" hook for "should return empty list of orphan delete markers if bucket is empty"::listLifecycleOrphanDeleteMarkers "before all" hook for "should return empty list of orphan delete markers if bucket is empty"

Stack Traces | 0.003s run time

connect ECONNREFUSED 127.0.0.1:8000

should return 409 when writing with an older microVersionId after objectPutTagging bumped it::CRR cascade : putMetadata should return 409 when writing with an older microVersionId after objectPutTagging bumped it

Stack Traces | 0.003s run time

connect ECONNREFUSED 127.0.0.1:8000

should delete the object if the source is Azure and if-unmodified-since condition is met::backbeat routes Batch Delete Route should delete the object if the source is Azure and if-unmodified-since condition is met

Stack Traces | 0.022s run time

connect ECONNREFUSED 127.0.0.1:8000

should not put delete tags if the source is not Azure and if-unmodified-since header is not provided::backbeat routes Batch Delete Route should not put delete tags if the source is not Azure and if-unmodified-since header is not provided

Stack Traces | 0.03s run time

connect ECONNREFUSED 127.0.0.1:8000

"after all" hook for "should return the last truncate list of current versions before a defined date"::listLifecycleCurrents with bucket versioning Enabled "after all" hook for "should return the last truncate list of current versions before a defined date"

Stack Traces | 0.032s run time

connect ECONNREFUSED 127.0.0.1:8000

should not put tags if the source is not Azure and if-unmodified-since condition is not met::backbeat routes Batch Delete Route should not put tags if the source is not Azure and if-unmodified-since condition is not met

Stack Traces | 0.033s run time

connect ECONNREFUSED 127.0.0.1:8000

should PUT metadata for a non-versioned bucket::backbeat routes backbeat PUT routes should PUT metadata for a non-versioned bucket

Stack Traces | 0.036s run time

ifError got unwanted exception: socket hang up

PUT metadata with "x-scal-replication-content: METADATA"header should replicate metadata only::backbeat routes backbeat PUT routes PUT metadata with "x-scal-replication-content: METADATA"header should replicate metadata only

Stack Traces | 0.038s run time

ifError got unwanted exception: socket hang up

"after all" hook for "should return trucated listing that excludes non-current versions stored in location2"::excludedDataStoreName "after all" hook for "should return trucated listing that excludes non-current versions stored in location2"

Stack Traces | 0.04s run time

connect ECONNREFUSED 127.0.0.1:8000

"after all" hook for "should return the fourth and last truncate list of orphan delete markers before a defined date"::listLifecycleOrphanDeleteMarkers "after all" hook for "should return the fourth and last truncate list of orphan delete markers before a defined date"

Stack Traces | 0.046s run time

connect ECONNREFUSED 127.0.0.1:8000

"after all" hook for "should return no orphan delete marker"::listLifecycle with non-current delete marker "after all" hook for "should return no orphan delete marker"

Stack Traces | 0.047s run time

connect ECONNREFUSED 127.0.0.1:8000

should PUT metadata and data if bucket is version suspended and x-scal-versioning-required is not set::backbeat routes backbeat PUT routes should PUT metadata and data if bucket is version suspended and x-scal-versioning-required is not set

Stack Traces | 0.049s run time

ifError got unwanted exception: socket hang up

should not delete the object if the source is Azure and if-unmodified-since condition is not met::backbeat routes Batch Delete Route should not delete the object if the source is Azure and if-unmodified-since condition is not met

Stack Traces | 0.049s run time

connect ECONNREFUSED 127.0.0.1:8000

should PUT metadata and data if bucket is not versioned and x-scal-versioning-required is not set::backbeat routes backbeat PUT routes should PUT metadata and data if bucket is not versioned and x-scal-versioning-required is not set

Stack Traces | 0.05s run time

ifError got unwanted exception: socket hang up

should update metadata of a current null version::backbeat routes null version should update metadata of a current null version

Stack Traces | 0.06s run time

socket hang up

should put tags if the source is not Azure and if-unmodified-since condition is met::backbeat routes Batch Delete Route should put tags if the source is not Azure and if-unmodified-since condition is met

Stack Traces | 0.063s run time

connect ECONNREFUSED 127.0.0.1:8000

should succeed normally when putData has no VersionId header::CRR cascade : baseline (no cascade headers) should succeed normally when putData has no VersionId header

Stack Traces | 0.079s run time

connect ECONNREFUSED 127.0.0.1:8000

should throw MicroVersionIdAlreadyStoredException on second write with the same microVersionId::CRR cascade : putMetadata should throw MicroVersionIdAlreadyStoredException on second write with the same microVersionId

Stack Traces | 0.08s run time

connect ECONNREFUSED 127.0.0.1:8000

should return 409 when writing with an older microVersionId::CRR cascade : putMetadata should return 409 when writing with an older microVersionId

Stack Traces | 0.083s run time

connect ECONNREFUSED 127.0.0.1:8000

should succeed and store updated metadata when putMetadata microVersionId is newer::CRR cascade : no errors should succeed and store updated metadata when putMetadata microVersionId is newer

Stack Traces | 0.09s run time

connect ECONNREFUSED 127.0.0.1:8000

"after all" hook for "should return no orphan delete marker"::listLifecycle with current delete marker version "after all" hook for "should return no orphan delete marker"

Stack Traces | 0.099s run time

connect ECONNREFUSED 127.0.0.1:8000

should batch delete a versioned AWS location::backbeat routes Batch Delete Route should batch delete a versioned AWS location

Stack Traces | 0.114s run time

connect ECONNREFUSED 127.0.0.1:8000

"after all" hook for "should return the null current versions"::listLifecycle if null version "after all" hook for "should return the null current versions"

Stack Traces | 0.115s run time

connect ECONNREFUSED 127.0.0.1:8000

should succeed normally when putMetadata has no MicroVersionId header::CRR cascade : baseline (no cascade headers) should succeed normally when putMetadata has no MicroVersionId header

Stack Traces | 0.166s run time

connect ECONNREFUSED 127.0.0.1:8000

"after all" hook for "should return truncated lists - part 3"::listLifecycleCurrents with bucket versioning enabled and maxKeys "after all" hook for "should return truncated lists - part 3"

Stack Traces | 0.179s run time

connect ECONNREFUSED 127.0.0.1:8000

"after all" hook for "should return list of non-current versions when bucket has a null current version"::listLifecycle with null current version after versioning suspended "after all" hook for "should return list of non-current versions when bucket has a null current version"

Stack Traces | 0.19s run time

connect ECONNREFUSED 127.0.0.1:8000

should set replication status to PENDING and preserve isReplica when bucket has CRR rules::CRR cascade : cascade setup for next location should set replication status to PENDING and preserve isReplica when bucket has CRR rules

Stack Traces | 0.211s run time

connect ECONNREFUSED 127.0.0.1:8000

"after all" hook for "should return truncated lists - part 2"::listLifecycleCurrents with bucket versioning enabled and delete object "after all" hook for "should return truncated lists - part 2"

Stack Traces | 0.216s run time

connect ECONNREFUSED 127.0.0.1:8000

"after all" hook for "should return the last truncate list of current versions before a defined date"::listLifecycleCurrents with bucket versioning Disabled "after all" hook for "should return the last truncate list of current versions before a defined date"

Stack Traces | 0.22s run time

connect ECONNREFUSED 127.0.0.1:8000

"after all" hook for "should treat a version-id-marker of "null" as no marker without crashing"::listLifecycleNonCurrents "after all" hook for "should treat a version-id-marker of "null" as no marker without crashing"

Stack Traces | 0.229s run time

connect ECONNREFUSED 127.0.0.1:8000

should succeed on first write when destination has no microVersionId::CRR cascade : putMetadata should succeed on first write when destination has no microVersionId

Stack Traces | 0.258s run time

connect ECONNREFUSED 127.0.0.1:8000

View the full list of 8 ❄️ flaky test(s)

"after each" hook for "should create a bunch of objects and their versions"::put and head object with versioning With default signature "after each" hook for "should create a bunch of objects and their versions"

Flake rate in main: 100.00% (Passed 0 times, Failed 41 times)

Stack Traces | 1.09s run time

The bucket you tried to delete is not empty.

"after each" hook for "should fail if trying to overwrite a delete marker"::MPU with x-scal-s3-version-id header With default signature "after each" hook for "should fail if trying to overwrite a delete marker"

Flake rate in main: 100.00% (Passed 0 times, Failed 98 times)

Stack Traces | 0.018s run time

We encountered an internal error. Please try again.

"after each" hook for "should fail if trying to overwrite a delete marker"::MPU with x-scal-s3-version-id header With v4 signature "after each" hook for "should fail if trying to overwrite a delete marker"

Flake rate in main: 100.00% (Passed 0 times, Failed 94 times)

Stack Traces | 0.139s run time

We encountered an internal error. Please try again.

"after each" hook for "should successfully replicate a version"::backbeat routes for replication (cross account) "after each" hook for "should successfully replicate a version"

Flake rate in main: 100.00% (Passed 0 times, Failed 2 times)

Stack Traces | 0.001s run time

connect ECONNREFUSED 127.0.0.1:8000

"after each" hook for "should successfully replicate a version"::backbeat routes for replication (same account) "after each" hook for "should successfully replicate a version"

Flake rate in main: 100.00% (Passed 0 times, Failed 2 times)

Stack Traces | 0.001s run time

connect ECONNREFUSED 127.0.0.1:8000

"before all" hook for "should return error when listing current versions if excluded-data-store-name is not in config"::excludedDataStoreName "before all" hook for "should return error when listing current versions if excluded-data-store-name is not in config"

Flake rate in main: 100.00% (Passed 0 times, Failed 2 times)

Stack Traces | 0.003s run time

connect ECONNREFUSED 127.0.0.1:8000

"before each" hook for "should successfully replicate a version"::backbeat routes for replication (cross account) "before each" hook for "should successfully replicate a version"

Flake rate in main: 100.00% (Passed 0 times, Failed 2 times)

Stack Traces | 0.001s run time

connect ECONNREFUSED 127.0.0.1:8000

"before each" hook for "should successfully replicate a version"::backbeat routes for replication (same account) "before each" hook for "should successfully replicate a version"

Flake rate in main: 100.00% (Passed 0 times, Failed 2 times)

Stack Traces | 0.002s run time

connect ECONNREFUSED 127.0.0.1:8000

To view more test analytics, go to the Test Analytics Dashboard
_{📋 Got 3 mins? Take this short survey to help us improve Test Analytics.}

claude · 2026-05-29T18:40:47Z

+});
+
+describe('CRR cascade — putMetadata', () => {
+    it('second write with the same microVersionId returns loop-detected', async () => {


Test names should start with "should" per project conventions (e.g. should return loop-detected on second write with the same microVersionId).

— Claude Code

claude · 2026-05-29T18:40:55Z

        "@hapi/joi": "^17.1.1",
        "@smithy/node-http-handler": "^3.0.0",
-        "arsenal": "git+https://github.com/scality/Arsenal#8.4.2",
+        "arsenal": "file:../Arsenal",


arsenal and @scality/cloudserverclient use file: local path references. These must be pinned to a tag or version before merging — file: references will break any install outside of your local workstation.

— Claude Code

claude · 2026-05-29T18:41:03Z

package.json: arsenal and @scality/cloudserverclient use file: local path references instead of pinned tags/versions — these will break installs for anyone else and must be updated before merge
- Pin arsenal to the Arsenal PR tag once merged (was 8.4.2)
- Pin @scality/cloudserverclient to a published version (was 1.0.7)
- tests/functional/backbeat/crrCascade.js: test names in it() blocks should start with should

Review by Claude Code

claude · 2026-06-01T11:54:15Z

    }
+
+    const encodedMicroVersionId = request.headers['x-scal-micro-version-id'];
+    const incomingRaw = encodedMicroVersionId ? decodeMicroVersionId(encodedMicroVersionId) : null;


The decode error handling here differs from putMetadata (line 574-575), which normalises the result immediately so incomingRaw is guaranteed non-Error. Here incomingRaw can hold an Error object, then is checked later with !(incomingRaw instanceof Error). Consider aligning with the putMetadata pattern for consistency.

— Claude Code

claude · 2026-06-01T11:54:29Z

        "@hapi/joi": "^17.1.1",
        "@smithy/node-http-handler": "^3.0.0",
-        "arsenal": "git+https://github.com/scality/Arsenal#8.4.2",
+        "arsenal": "file:../Arsenal",


arsenal and @scality/cloudserverclient point to local file:../ paths. These must be pinned to git tags before merging — anyone cloning this repo won't have these sibling directories.

— Claude Code

claude · 2026-06-01T11:54:40Z

package.json: arsenal and @scality/cloudserverclient point to local file:../ paths — must be pinned to git tags before merging.
- lib/utilities/collectResponseHeaders.js:103: Cascade replicas without a next hop have status: '' and isReplica: true, but the outer if only checks status (falsy for empty string), so x-amz-replication-status: REPLICA header will be missing from S3 responses for these objects.
- lib/routes/routeBackbeat.js:438: putData and putMetadata handle decodeMicroVersionId error cases differently — consider aligning for consistency.
- tests/functional/backbeat/crrCascade.js: Missing after() hook to clean up the three test buckets created in before().

Review by Claude Code

claude · 2026-06-18T14:52:25Z

Arsenal is pinned to a raw commit hash (f6b6e2a…) instead of a semver tag — violates the project's dependency pinning convention for git-based deps.
- Pin to a tag once the Arsenal release containing the required changes is cut.
cloudserverclient.tgz is committed but never referenced — only scality-cloudserverclient-v1.0.9.tgz is used in package.json and Dockerfile.
- Remove the orphan file.
Both .tgz binary artifacts are checked into git, inflating history permanently.
- Consider publishing @scality/cloudserverclient to the registry or using a git ref like other Scality deps.
Unused output variable in tests/functional/backbeat/crrCascade.js:228.
- Drop the assignment: await putMetadata(key, newerMvId);
Inconsistent error-assertion pattern in the same describe block: line 139 uses assert.rejects, line 158 uses try/catch + assert.fail.
- Use assert.rejects in both tests for consistency.

Review by Claude Code

claude · 2026-06-18T15:22:08Z

package.json:40 — Arsenal is pinned to a commit hash instead of a tag. Git-based deps should pin to a tag per project conventions.
- cloudserverclient.tgz — This file is added but never referenced anywhere (package.json and Dockerfile only reference scality-cloudserverclient-v1.0.9.tgz). Remove the orphan file.
- lib/routes/routeBackbeat.js:638 — Inconsistent isReplica check uses truthy (isReplica) while lines 654, 671, and 750 use strict equality (isReplica === true). Use strict equality for consistency.
- tests/functional/backbeat/crrCascade.js:228 — output variable assigned but never used.

Review by Claude Code

maeldonn · 2026-06-24T07:54:47Z

+            // as cascade targets because they use the MultiBackend S3 path which
+            // bypasses the putData/putMetadata routes, so loop detection cannot fire
+            // on those destinations.
+            const BLOCKED_LOCATION_TYPES = ['location-scality-ring-s3-v1', 'location-scality-artesca-s3-v1'];


Could it be tested on a real lab ?

should be honestly, i think i need to double check this together with the design and the code

maeldonn · 2026-06-24T07:55:52Z

        replicationInfo: getReplicationInfo(config,
            objectKey, bucketMD, false, size, null, null, authInfo),
        overheadField,
+        updateMicroVersionId: true,


Do we really need this ?

yes, actually this is important, I added this after making my tests in codespaces :
Without this :
You put an object : object isn't assigned an micro version Id
You setup the whole replication, backbeat picks up that source object, it doesn't have any microversion id so cloudserver just doesn't try to process it as a potential cascade replication

should "new" objects not keep having an empty microVersionId (to avoid wasting metadata space)?
and just consider "no micro version id" is the oldest micro versionId (the only thing it cannot compare to is another no micro version id - but that would not happen on new object, each get their own versionId)

in case of un-versioned buckets (i.e. only master objects), we may need to update the micro version id (because we have no version id) ; however there is no replication in that case, so no problem not to do it

Similar thread here: https://github.com/scality/citadel/pull/349#discussion_r3137680994

~~Should be done in objectPut instead: 7a63acf (#6178)~~

We discussed this a bit with Maël.
I think we could try to not do it all the time, and do it only for putObject (but not even sure).
But we were wondering what happens if we don't write microVersionId on putObject : how do we compare two objects that don't have any micro version ID, it may be possible on the first replication to consider no micro version id => source is newer, but then we must write the microVersionID anyways to block loop and make later write work.
Also in the design we said microVersionId would necessarily be used for this feature only but more generally to be able to track and compare update time, I'm very worried we're gonna have issues later if we start writing microVersionID only on certain conditiion. Actually the code in arsenal, backbeat and cloudserver is already filled with quite a lot of defensive and smelly if (microVersionID) because we never bothered adding this from the start

maeldonn · 2026-06-24T07:58:35Z

+            request.resume();
+            return _respondWithHeaders(
+                response,
+                { code: MicroVersionIdAlreadyStoredException.name,
+                    message: 'incoming microVersionId already at destination' },
+                {},
+                log,
+                callback,
+                409,
+            );


could you remove duplication to simplify here ?

Ok I did something, you take a look but honestly it's really not that great 🤔

the code is completely duplicated, the only difference is really name of exception and "text" of message.

as discussed in cloudserverclient, do we really need cloudserver to make that distinction? just returning the same error (micro version id conflict) AND the micro version id of the object stored allows the caller to make the distinction, if they need - without duplication.

ahhh, I missed the extra type MicroVersionIdAlreadyStoredException, c.f. https://github.com/scality/cloudserverclient/pull/24/changes#r3496549728

we had the discussion and ended adding microVersionId in StaleMicroVersionIdException, but it is useless if we generate 2 kinds of errors...
→ IMHO we should drop MicroVersionIdAlreadyStoredException, which allows deduplicating here and simplifying backbeat?

otherwise we shoud still dedup, something like:

Suggested change

request.resume();

return _respondWithHeaders(

response,

{ code: MicroVersionIdAlreadyStoredException.name,

message: 'incoming microVersionId already at destination' },

{},

log,

callback,

409,

);

if (cmp !=== Ordering.NEWER) {

request.resume();

return _respondWithHeaderCrrConflict(

response, log, callback,

cmp === Ordering.EQUAL ? MicroVersionIdAlreadyStoredException.name : StaleMicroVersionIdException.name,

'incoming microVersionId already at destination',

);

}

Sending back the microVersionID is indeed not super useful, I added it because it was suggested it could become useful or nice to have the info for the caller. I'm not really gonna focus on this to much, i can remove it or keep it, imo I think it's fine that an api returns it.

But for the double error, well tbh i don't really mind either as I just wanna put an end to this feature, but for me it's better to have backbeat check the errors like this :

Than having it just receive a microVersion id, then does another loop if microversion == null, if microversion < > xxx, then we don't do exactly the same thing (cbOnce(cascadeLoopDetected) vs cbOnce(cascadeDataStale)).

In the screenshot, we directly have errors that we can nicely catch and that's pretty much it.

I just see calling the client like calling any functions, and if the function I call return an error, I want the error to be as detailed as possible and not redo the checks that was already done, because anyways cloudserver has to do those comparisons here.

I will recheck the suggested simpification after we settle the discussion, not fully sure it should be done though because compare can return 4 values
older
younger
equal
not comparable

so doing this cmp !=== Ordering.NEWER
still leaves room for NOT_COMPARABLE, I think it's safer to assert on what we want that exclude only value

maeldonn

LGTM. Please bump package.json and create a new release. Could you just confirm that the location guard is working ?

bert-e · 2026-06-29T08:49:02Z

Waiting for approval

The following approvals are needed before I can proceed with the merge:

the author
2 peers

francoisferrand · 2026-06-24T15:13:03Z

+    const incomingVersionIdEncoded = request.headers['x-scal-version-id'];
+    const decoded = incomingVersionIdEncoded ? decode(incomingVersionIdEncoded) : null;
+    const incomingVersionIdDecoded = decoded instanceof Error ? null : decoded;
+    if (incomingVersionIdDecoded && objMd && objMd.versionId === incomingVersionIdDecoded) {


objMd.versionId === incomingVersionIdDecoded

Can this condition actually fail?

Is it really part of the condition?

AFAIU, versionId is used (or should be?) to find the existing objMD:

so if not found, we would get objMD=null ;

and if found, it should have the versionID...

Unless there is a some logic here which gets the matching version if it exist, else the latest one : in that case objMd.versionId !== incomingVersionIdDecoded means we actually did not an object already

→ should clarify how we get there, and nice if we can drop this condition
(remember that with CRR with cannot work in non-versioned buckets -so no "overwrites"-, and that versions may be replicated out of order)

I rewrote some part of the if statement into 2 stages, but your comment still stands.

I am not sure i understand it though, I think you are saying that if we were able to get objMd, then necessarily objMd will be equal to incomingVersionIdDecoded ?

objMd is obtained through a middleware, from the provided bucket + the key, and it's the latest available version of that bucket

the x-scal-micro-version-id is anything people using the client decide to put inside. I don't see a situation where we would skip checking objMd.version === incomingVersionId

francoisferrand · 2026-06-30T06:00:53Z

        replicationInfo: getReplicationInfo(config,
            objectKey, bucketMD, false, size, null, null, authInfo),
        overheadField,
+        updateMicroVersionId: true,


should "new" objects not keep having an empty microVersionId (to avoid wasting metadata space)?
and just consider "no micro version id" is the oldest micro versionId (the only thing it cannot compare to is another no micro version id - but that would not happen on new object, each get their own versionId)

in case of un-versioned buckets (i.e. only master objects), we may need to update the micro version id (because we have no version id) ; however there is no replication in that case, so no problem not to do it

francoisferrand · 2026-06-30T06:02:59Z

+
+    const incomingVersionIdEncoded = request.headers['x-scal-version-id'];
+    const decoded = incomingVersionIdEncoded ? decode(incomingVersionIdEncoded) : null;
+    const incomingVersionIdDecoded = decoded instanceof Error ? null : decoded;


should we not actually fail if the version id cannot be decoded? (this would be a bad request)

yes actually i changed the single if into 2 ifs :
If the versionId is provided, but we can't decode it, it means something is wrong and we shouldn't continue anything

francoisferrand · 2026-06-30T06:07:15Z

 function putMetadata(request, response, bucketInfo, objMd, log, callback) {
+    const { bucketName, objectKey } = request;
+
+    const encodedMicroVersionId = request.headers['x-scal-micro-version-id'];


we probably need to differentiate between

the absence of microVersionId (ie. x-scal-micro-version-id is not present in the request) → no extra check

microVersionId is empty (something like x-scal-micro-version-id: "", when referring to the first metadata revision when object was created) → need the extra check, and check if the object already has newer micro version id (i.e. either it does not have one → "equal", or it does → "newer")

I change the code a bit to do what you mention in the first point, and also return an error when the header is present but fail to be decoded like in putData.

For the other point,
The current implementation is : new source will always have a microVersionId, it's talked about in another comment at the top of this review, but I don't see how we can properly deal with empty microversion ids on new objects written after this feature is added, without having issues later. It means we would have situation like

A->B->C
I put on A, A has no microVersionID, but replicates to B and C which now have a microVersionID.
But A still doesn't have a microVersionID. What happens if there is a loop configuration and C goes back to A
What happens on the second write on A when a first write has already replicated on B and C ? B and C will have a microVersionID but A won't ?

It seems to me that deciding to not assign a microVersionID on all new putObject writes is gonna get real tricky in the long run

francoisferrand · 2026-06-30T06:17:13Z

+            request.resume();
+            return _respondWithHeaders(
+                response,
+                { code: MicroVersionIdAlreadyStoredException.name,
+                    message: 'incoming microVersionId already at destination' },
+                {},
+                log,
+                callback,
+                409,
+            );


the code is completely duplicated, the only difference is really name of exception and "text" of message.

as discussed in cloudserverclient, do we really need cloudserver to make that distinction? just returning the same error (micro version id conflict) AND the micro version id of the object stored allows the caller to make the distinction, if they need - without duplication.

francoisferrand · 2026-06-30T06:18:10Z

+            request.resume();
+            return _respondWithHeaders(
+                response,
+                { code: MicroVersionIdAlreadyStoredException.name,
+                    message: 'incoming microVersionId already at destination' },
+                {},
+                log,
+                callback,
+                409,
+            );


ahhh, I missed the extra type MicroVersionIdAlreadyStoredException, c.f. https://github.com/scality/cloudserverclient/pull/24/changes#r3496549728

we had the discussion and ended adding microVersionId in StaleMicroVersionIdException, but it is useless if we generate 2 kinds of errors...
→ IMHO we should drop MicroVersionIdAlreadyStoredException, which allows deduplicating here and simplifying backbeat?

otherwise we shoud still dedup, something like:

Suggested change

request.resume();

return _respondWithHeaders(

response,

{ code: MicroVersionIdAlreadyStoredException.name,

message: 'incoming microVersionId already at destination' },

{},

log,

callback,

409,

);

if (cmp !=== Ordering.NEWER) {

request.resume();

return _respondWithHeaderCrrConflict(

response, log, callback,

cmp === Ordering.EQUAL ? MicroVersionIdAlreadyStoredException.name : StaleMicroVersionIdException.name,

'incoming microVersionId already at destination',

);

}

francoisferrand · 2026-06-30T06:30:19Z

+                nextReplInfo.backends = nextReplInfo.backends.filter(b => {
+                    const loc = config.locationConstraints[b.site];
+                    return !loc || !BLOCKED_LOCATION_TYPES.includes(loc.type);
+                });


this logic should be in getReplicationInfo, this is the function responsible to build the list of backend/destinations. Doing it there will also avoid create a backend entry only to remove it.

Are you sure you wanna do this ? It means I have to add some kind of flag to getReplicationInfo to do the current logic in getReplicationInfo 🤔

Ok I see, maybe it can be done cleanly if, in getReplicationInfo.js I add a helper function, leave the existing function almost as it is and just call that extra helper at the end of getReplicationInfo if the flag is on ?

francoisferrand · 2026-06-30T06:31:54Z

+            // These S3-compatible Scality locations are excluded
+            // as cascade targets because they use the MultiBackend S3 path which
+            // bypasses the putData/putMetadata routes, so loop detection cannot fire
+            // on those destinations.


is this part of the design? I may be wrong, but I thought we wanted (needed maybe, to be check with product team) to trigger multi-backend replication after CRR ?
→ please double check

it's here https://github.com/scality/citadel/pull/349/changes#diff-f4fbff9b43d54385a8778f028f6950744393bb5235c5860afa7eec1b89072f83R266

but yeah i need to triple check it because yes i don't really like this part with these hardcoded locations

Issue: CLDSRV-897

claude · 2026-06-30T19:05:36Z

+        // status to PENDING so the queue populator here picks it up for the
+        // next hop. If not, clear the source-side replicationInfo fields
+        // Always mark isReplica=true.
+        if (incomingMicroVersionId) {


incomingMicroVersionId is declared with const inside the if (encodedMicroVersionId) block (line 596), which makes it block-scoped to that if block. This reference at line 826 is outside that scope (it's inside the _getRequestPayload callback), so it will throw ReferenceError: incomingMicroVersionId is not defined at runtime.

This affects ALL putMetadata requests through the backbeat route — both with and without cascade headers — and will crash the server process.

Simplest fix: use the function-scoped encodedMicroVersionId here since only a truthiness check is needed.

Suggested change

if (incomingMicroVersionId) {

if (encodedMicroVersionId) {

SylvainSenechal commented May 29, 2026

View reviewed changes

Comment thread lib/api/apiUtils/object/versioning.js Outdated

SylvainSenechal commented May 29, 2026

View reviewed changes

Comment thread lib/routes/routeBackbeat.js

claude Bot reviewed May 29, 2026

View reviewed changes

SylvainSenechal commented May 29, 2026

View reviewed changes

Comment thread lib/routes/routeBackbeat.js

SylvainSenechal commented May 29, 2026

View reviewed changes

Comment thread lib/routes/routeBackbeat.js Outdated

SylvainSenechal commented May 29, 2026

View reviewed changes

SylvainSenechal mentioned this pull request May 29, 2026

Upgrade microVersionId to timestamp-ordered format and add isReplica scality/Arsenal#2628

Merged

SylvainSenechal changed the title ~~Improvement/cldsrv 897~~ Add CRR Cascaded capabilities May 29, 2026

SylvainSenechal requested review from a team, delthas and maeldonn May 29, 2026 18:11

SylvainSenechal force-pushed the improvement/CLDSRV-897 branch from c15fb2b to 7912480 Compare May 29, 2026 18:38

claude Bot reviewed May 29, 2026

View reviewed changes

SylvainSenechal mentioned this pull request May 29, 2026

Added headers for CRR Cascaded scality/cloudserverclient#24

Merged

SylvainSenechal force-pushed the improvement/CLDSRV-897 branch from 7912480 to 973261a Compare June 1, 2026 11:51

claude Bot reviewed Jun 1, 2026

View reviewed changes

Comment thread tests/functional/backbeat/crrCascade.js

claude Bot reviewed Jun 1, 2026

View reviewed changes

Comment thread lib/utilities/collectResponseHeaders.js Outdated

claude Bot reviewed Jun 18, 2026

View reviewed changes

Comment thread package.json Outdated

claude Bot reviewed Jun 18, 2026

View reviewed changes

Comment thread package.json Outdated

claude Bot reviewed Jun 18, 2026

View reviewed changes

Comment thread tests/functional/backbeat/crrCascade.js

claude Bot reviewed Jun 18, 2026

View reviewed changes

Comment thread tests/functional/backbeat/crrCascade.js Outdated

delthas mentioned this pull request Jun 18, 2026

Unblock arsenal bumps on 9.3: realign replication tests for CRR ObjectMD refactor #6193

Closed

SylvainSenechal force-pushed the improvement/CLDSRV-897 branch from 92f01c0 to 365213b Compare June 18, 2026 15:19

claude Bot reviewed Jun 18, 2026

View reviewed changes

Comment thread package.json Outdated

claude Bot reviewed Jun 18, 2026

View reviewed changes

Comment thread lib/routes/routeBackbeat.js Outdated

claude Bot reviewed Jun 18, 2026

View reviewed changes

Comment thread tests/functional/backbeat/crrCascade.js Outdated

SylvainSenechal force-pushed the improvement/CLDSRV-897 branch from 365213b to 37068a8 Compare June 22, 2026 09:57

github-advanced-security AI found potential problems Jun 22, 2026

View reviewed changes

Comment thread scripts/crr-cascade-test.ts Fixed

Comment thread scripts/crr-cascade-test.ts Fixed

SylvainSenechal force-pushed the improvement/CLDSRV-897 branch 2 times, most recently from 3e4bd1d to 9840ffa Compare June 22, 2026 11:49

SylvainSenechal requested a review from a team June 22, 2026 13:54

SylvainSenechal force-pushed the improvement/CLDSRV-897 branch 2 times, most recently from 391c544 to 3c698dc Compare June 23, 2026 17:54

maeldonn reviewed Jun 24, 2026

View reviewed changes

SylvainSenechal force-pushed the improvement/CLDSRV-897 branch from 3c698dc to c8acd08 Compare June 25, 2026 19:23

SylvainSenechal requested a review from maeldonn June 25, 2026 19:23

claude Bot reviewed Jun 25, 2026

View reviewed changes

Comment thread lib/routes/routeBackbeat.js Outdated

SylvainSenechal force-pushed the improvement/CLDSRV-897 branch from c8acd08 to 51638dd Compare June 26, 2026 09:01

maeldonn approved these changes Jun 29, 2026

View reviewed changes

francoisferrand reviewed Jun 30, 2026

View reviewed changes

Implement CRR Cascaded feature

afa7f2e

Issue: CLDSRV-897

SylvainSenechal force-pushed the improvement/CLDSRV-897 branch from 51638dd to afa7f2e Compare June 30, 2026 19:00

SylvainSenechal requested a review from francoisferrand June 30, 2026 19:00

claude Bot reviewed Jun 30, 2026

View reviewed changes

	"arsenal": "file:../Arsenal",
	"arsenal": "git+https://github.com/scality/Arsenal#8.4.2",

Uh oh!

Conversation

SylvainSenechal commented May 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

bert-e commented May 29, 2026

Hello sylvainsenechal,

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

claude Bot May 29, 2026

Choose a reason for hiding this comment

Uh oh!

claude Bot May 29, 2026

Choose a reason for hiding this comment

Uh oh!

claude Bot May 29, 2026

Choose a reason for hiding this comment

Uh oh!

claude Bot May 29, 2026

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

claude Bot commented May 29, 2026

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

codecov Bot commented May 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

❌ 103 Tests Failed:

Uh oh!

claude Bot May 29, 2026

Choose a reason for hiding this comment

Uh oh!

claude Bot May 29, 2026

Choose a reason for hiding this comment

Uh oh!

claude Bot commented May 29, 2026

Uh oh!

claude Bot Jun 1, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

claude Bot Jun 1, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

claude Bot commented Jun 1, 2026

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

claude Bot commented Jun 18, 2026

Uh oh!

Uh oh!

Uh oh!

Uh oh!

claude Bot commented Jun 18, 2026

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

SylvainSenechal commented May 29, 2026 •

edited

Loading

codecov Bot commented May 29, 2026 •

edited

Loading

maeldonn Jun 30, 2026 •

edited

Loading

SylvainSenechal Jun 30, 2026 •

edited

Loading