CLDSRV-1051: Map DEEP_ARCHIVE to the deep-archive location by francoisferrand · Pull Request #6344 · scality/cloudserver

francoisferrand · 2026-10-27T08:27:16Z

Fixup for #6329, which maps the AWS archive storage classes to a cold location with the same name in lower case. For DEEP_ARCHIVE that gave deep_archive, but that location can't be created, as management API only accepts location names matching ^[a-z][a-z0-9-]+$: so the mapping could never be used.

DEEP_ARCHIVE now maps to deep-archive, while GLACIER still maps to glacier.

Issue: CLDSRV-1051

bert-e · 2026-10-27T08:27:20Z

Hello francoisferrand,

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	⭐
`/bypass_source_branch_lineage`	Bypass the cross-branch contamination check	⭐
`/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.
`/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.

codecov · 2026-10-27T08:29:40Z

❌ 2 Tests Failed:

Tests completed	Failed	Passed	Skipped
19047	2	19045	959

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

Abort MPU - Race Conditions With v4 signature::"after each" hook for "should handle abort during concurrent CompleteMPU without corruption"

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

Stack Traces | 0.016s run time

The specified multipart upload does not exist. The upload ID might be invalid, or the multipart upload might have been aborted or completed.
NoSuchUpload: The specified multipart upload does not exist. The upload ID might be invalid, or the multipart upload might have been aborted or completed.
    at S3RestXmlProtocol.handleError (.../cloudserver/cloudserver/node_modules/@.../submodules/protocols/index.js:1349:27)
    at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
    at async S3RestXmlProtocol.deserializeResponse (.../cloudserver/cloudserver/node_modules/@.../submodules/protocols/index.js:406:13)
    at async .../cloudserver/cloudserver/node_modules/@.../submodules/schema/index.js:23:24
    at async .../cloudserver/cloudserver/node_modules/@.../submodules/s3/index.js:366:20
    at async .../cloudserver/cloudserver/node_modules/@.../submodules/retry/index.js:175:50
    at async .../cloudserver/cloudserver/node_modules/@.../submodules/s3/index.js:62:28
    at async .../cloudserver/cloudserver/node_modules/@.../submodules/s3/index.js:89:20
    at async .../cloudserver/cloudserver/node_modules/@.../submodules/client/index.js:125:26
    at async cleanupVersionedBucket (test/object/abortMPU.js:62:5)
    at async Context.<anonymous> (test/object/abortMPU.js:875:13)

Abort MPU - Race Conditions With v4 signature::should handle abort during concurrent CompleteMPU without corruption

Flake rate in main: 40.00% (Passed 3 times, Failed 2 times)

Stack Traces | 0.071s run time

No MPU metadata should remain

1 !== 0


      + expected - actual

      -1
      +0
      
AssertionError [ERR_ASSERTION]: No MPU metadata should remain

1 !== 0

    at Context.<anonymous> (test/object/abortMPU.js:960:20)
    at process.processTicksAndRejections (node:internal/process/task_queues:104:5)

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

bert-e · 2026-10-27T08:33:21Z

Request integration branches

Waiting for integration branch creation to be requested by the user.

To request integration branches, please comment on this pull request with the following command:

/create_integration_branches

Alternatively, the /approve and /create_pull_requests commands will automatically
create the integration branches.

The AWS archive storage classes are mapped to a cold location of the same lower-case name, which gave `deep_archive` for DEEP_ARCHIVE. Location names must match `^[a-z][a-z0-9-]+$` (management API), so such a location can never be created and the mapping was unusable. DEEP_ARCHIVE now maps to `deep-archive`. The mapping is spelled out explicitly rather than derived from the AWS name, and both lookup directions go through it. Issue: CLDSRV-1051

Issue: CLDSRV-1051

francoisferrand · 2026-10-27T15:38:36Z

/approve

bert-e · 2026-10-27T15:57:19Z

I have successfully merged the changeset of this pull request
into targetted development branches:

✔️ development/9.5
✔️ development/9.6

The following branches have NOT changed:

development/7.10
development/7.4
development/7.70
development/8.8
development/9.0
development/9.1
development/9.2
development/9.3
development/9.4

This pull request did not target the following hotfix branch(es) so they
were left untouched:

hotfix/7.8.0
hotfix/9.0.7
hotfix/7.4.0
hotfix/7.2.0
hotfix/9.2.36
hotfix/7.10.27
hotfix/7.70.45
hotfix/7.10.1
hotfix/7.4.6
hotfix/7.10.15
hotfix/7.10.30
hotfix/7.7.0
hotfix/7.70.11
hotfix/7.4.8
hotfix/7.10.8
hotfix/7.4.2
hotfix/7.6.0
hotfix/7.9.0
hotfix/7.4.7
hotfix/8.8.45
hotfix/7.70.51
hotfix/7.10.28
hotfix/7.10.2
hotfix/7.10.49
hotfix/9.3.13
hotfix/7.4.1
hotfix/6.4.7
hotfix/7.4.5
hotfix/7.10.3
hotfix/9.0.32
hotfix/7.10.4
hotfix/7.4.10
hotfix/7.4.9
hotfix/7.70.73
hotfix/7.4.4
hotfix/7.70.21
hotfix/7.10.0
hotfix/7.4.3
hotfix/9.2.24

Please check the status of the associated issue CLDSRV-1051.

Goodbye francoisferrand.

The following options are set: approve

francoisferrand requested review from a team, delthas and maeldonn October 27, 2026 08:27

delthas approved these changes Oct 27, 2026

View reviewed changes

scality deleted a comment from bert-e Oct 27, 2026

francoisferrand force-pushed the bugfix/CLDSRV-1051-deep-archive-location branch from c680e96 to 10fadf4 Compare October 27, 2026 10:24

maeldonn approved these changes Oct 27, 2026

View reviewed changes

francoisferrand added 2 commits October 27, 2026 16:37

Release 9.5.2

76a22bf

Issue: CLDSRV-1051

francoisferrand force-pushed the bugfix/CLDSRV-1051-deep-archive-location branch from 10fadf4 to 76a22bf Compare October 27, 2026 15:38

bert-e merged commit 76a22bf into development/9.5 Oct 27, 2026
37 checks passed

bert-e deleted the bugfix/CLDSRV-1051-deep-archive-location branch October 27, 2026 15:57

eve-ci-cd Bot had a problem deploying to zenko/improvement/[email protected] October 27, 2026 17:54 Failure

Navigation Menu

Repository navigation

CLDSRV-1051: Map DEEP_ARCHIVE to the deep-archive location - #6344

CLDSRV-1051: Map DEEP_ARCHIVE to the deep-archive location#6344
bert-e merged 2 commits into
development/9.5from
bugfix/CLDSRV-1051-deep-archive-location

francoisferrand commented Oct 27, 2026 •

edited

Loading

Uh oh!

bert-e commented Oct 27, 2026

Uh oh!

codecov Bot commented Oct 27, 2026 •

edited

Loading

Uh oh!

bert-e commented Oct 27, 2026

Uh oh!

francoisferrand commented Oct 27, 2026

Uh oh!

bert-e commented Oct 27, 2026

Uh oh!

Uh oh!

This branch had an error being deployed

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Conversation

francoisferrand commented Oct 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

bert-e commented Oct 27, 2026

Hello francoisferrand,

Uh oh!

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

Uh oh!

❌ 2 Tests Failed:

Uh oh!

bert-e commented Oct 27, 2026

Request integration branches

Uh oh!

francoisferrand commented Oct 27, 2026

Uh oh!

bert-e commented Oct 27, 2026

Uh oh!

Uh oh!

This branch had an error being deployed

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

francoisferrand commented Oct 27, 2026 •

edited

Loading

codecov Bot commented Oct 27, 2026 •

edited

Loading