Skip to content

Bump arsenal to 8.4.11 (CRR reverted; unblocks 9.3)#6198

Merged
bert-e merged 1 commit into
development/9.3from
improvement/CLDSRV-929/bump-arsenal-8-4-11
Jun 22, 2026
Merged

Bump arsenal to 8.4.11 (CRR reverted; unblocks 9.3)#6198
bert-e merged 1 commit into
development/9.3from
improvement/CLDSRV-929/bump-arsenal-8-4-11

Conversation

@delthas

@delthas delthas commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

What

Bump the arsenal dependency on development/9.3 from 8.4.4 to 8.4.11.

Why

8.4.11 reverts the multi-destination CRR changes (arsenal ARSN-600 / scality/Arsenal#2651) that were not backward-compatible for consumers still on the 8.4 line. With CRR reverted, 9.3 consumes 8.4.x again with no code or test changes — superseding the earlier "realign the replication tests" approach (closed PR #6193).

Verified locally against 8.4.11: full unit suite 5097 passing, 0 failing.

Pin detail

package.json pins the #8.4.11 version ref. Since the tag isn't published yet, yarn.lock resolves it to the ARSN-600 release commit (5981b886) so yarn install --frozen-lockfile works today; when arsenal tags 8.4.11 at that commit, nothing changes.

⚠️ Merge dependency

Do not merge until arsenal 8.4.11 is released/tagged (ARSN-600 / scality/Arsenal#2651 merged). CRR continues on arsenal 8.5 → 9.4 moves to 8.5.0-preview.1 on its waterfall branch.

Issue: CLDSRV-929

Pick up arsenal 8.4.11, which reverts the multi-destination CRR changes
(ARSN-600 / scality/Arsenal#2651) that were not backward-compatible for the 9.3
line. With CRR reverted, 9.3 consumes 8.4.x again with no code or test changes
(full unit suite green).

package.json pins the #8.4.11 version ref; yarn.lock resolves it to the
ARSN-600 release commit so installs work before the 8.4.11 tag is published
(same commit, nothing to change once tagged).

Issue: CLDSRV-929
@bert-e

bert-e commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

Hello delthas,

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.

@bert-e

bert-e commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

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.

@delthas delthas requested review from a team, SylvainSenechal and maeldonn June 22, 2026 09:31
@codecov

codecov Bot commented Jun 22, 2026

Copy link
Copy Markdown

❌ 2 Tests Failed:

Tests completed Failed Passed Skipped
8483 2 8481 0
View the full list of 2 ❄️ flaky test(s)
"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 76 times)

Stack Traces | 0.015s 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 66 times)

Stack Traces | 0.015s run time
We encountered an internal error. Please try again.

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

@SylvainSenechal SylvainSenechal left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

btw, why is it arsenal 8.4.11 and not 8.4.10 ? I think the messed up release is 8.4.9

@delthas

delthas commented Jun 22, 2026

Copy link
Copy Markdown
Contributor Author

btw, why is it arsenal 8.4.11 and not 8.4.10 ? I think the messed up release is 8.4.9

I released a 8.4.10 with some other changes inbetween.

@delthas

delthas commented Jun 22, 2026

Copy link
Copy Markdown
Contributor Author

/approve

@bert-e

bert-e commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

In the queue

The changeset has received all authorizations and has been added to the
relevant queue(s). The queue(s) will be merged in the target development
branch(es) as soon as builds have passed.

The changeset will be merged in:

  • ✔️ development/9.3

  • ✔️ development/9.4

The following branches will NOT be impacted:

  • development/7.10
  • development/7.4
  • development/7.70
  • development/8.8
  • development/9.0
  • development/9.1
  • development/9.2

This pull request does not target the following hotfix branch(es) so they
will be left untouched:

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

There is no action required on your side. You will be notified here once
the changeset has been merged. In the unlikely event that the changeset
fails permanently on the queue, a member of the admin team will
contact you to help resolve the matter.

IMPORTANT

Please do not attempt to modify this pull request.

  • Any commit you add on the source branch will trigger a new cycle after the
    current queue is merged.
  • Any commit you add on one of the integration branches will be lost.

If you need this pull request to be removed from the queue, please contact a
member of the admin team now.

The following options are set: approve

@bert-e

bert-e commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

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

  • ✔️ development/9.3

  • ✔️ development/9.4

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

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

Goodbye delthas.

@bert-e bert-e merged commit 2937b07 into development/9.3 Jun 22, 2026
60 of 61 checks passed
@bert-e bert-e deleted the improvement/CLDSRV-929/bump-arsenal-8-4-11 branch June 22, 2026 16:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants