Skip to content

Bump arsenal to 8.5.6 to support V2 replication bucket metadata - #1334

Merged
bert-e merged 3 commits into
development/8.3from
bugfix/UTAPI-124/multi-crr
Jul 27, 2026
Merged

Bump arsenal to 8.5.6 to support V2 replication bucket metadata#1334
bert-e merged 3 commits into
development/8.3from
bugfix/UTAPI-124/multi-crr

Conversation

@maeldonn

Copy link
Copy Markdown

Align with the arsenal version cloudserver ships. Arsenal >= 8.4.7 writes
bucket replication metadata in the V2 (multi-destination CRR) format
without the deprecated top-level destination. Arsenal 8.2.28 asserted that
field unconditionally and crashed utapi when reading such buckets.

Issue: UTAPI-124

maeldonn added 2 commits July 23, 2026 18:23
Align with the arsenal version cloudserver ships. Arsenal >= 8.4.7 writes
bucket replication metadata in the V2 (multi-destination CRR) format
without the deprecated top-level destination. Arsenal 8.2.28 asserted that
field unconditionally and crashed utapi when reading such buckets.

Issue: UTAPI-124
Cover getBucket/bucketExists against V1, V2 single-destination and
multi-destination CRR bucket metadata, plus error paths.

Issue: UTAPI-124
@maeldonn
maeldonn requested review from a team, SylvainSenechal, delthas and leif-scality July 23, 2026 16:25
@bert-e

bert-e commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

Hello maeldonn,

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.

@scality scality deleted a comment from bert-e Jul 23, 2026
@bert-e

bert-e commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

Waiting for approval

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

  • the author

  • 2 peers

@maeldonn
maeldonn requested review from benzekrimaha and removed request for delthas July 23, 2026 16:32
@maeldonn
maeldonn marked this pull request as ready for review July 23, 2026 16:34
@maeldonn

maeldonn commented Jul 23, 2026

Copy link
Copy Markdown
Author

@leif-scality I think we should target a new development/8.3 branch for this. What do you think?

@SylvainSenechal

Copy link
Copy Markdown

@leif-scality I think we should target a new development/8.3 branch for this. What do you think?

ye can

@benzekrimaha benzekrimaha 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.

LGTM, well done

@leif-scality

Copy link
Copy Markdown

So this PR will make utapi not compatible with cloudserver 9.3 and previous versions? Only cloudserver 9.4 will work after this? Maybe we should do a development/8.3

@nicolas2bert

@leif-scality

Copy link
Copy Markdown

So this PR will make utapi not compatible with cloudserver 9.3 and previous versions? Only cloudserver 9.4 will work after this? Maybe we should do a development/8.3

@nicolas2bert

This fixed the integration problem
Federation build: https://github.com/scality/Federation/pull/6993
Green Integration: https://github.com/scality/Integration/actions/runs/30082259417

@leif-scality leif-scality left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

LGTM, but we need merge it in a new development/8.3

@bert-e

bert-e commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

Waiting for approval

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

  • the author

  • 2 peers

The following reviewers are expecting changes from the author, or must review again:

@leif-scality
leif-scality changed the base branch from development/8.2 to development/8.3 July 27, 2026 10:55
@bert-e

bert-e commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

Incorrect fix version

The Fix Version/s in issue UTAPI-124 contains:

  • 8.2.7

Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:

  • 8.3.0

Please check the Fix Version/s of UTAPI-124, or the target
branch of this pull request.

@bert-e

bert-e commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

Waiting for approval

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

  • the author

  • 2 peers

@maeldonn

Copy link
Copy Markdown
Author

/approve

1 similar comment
@maeldonn

Copy link
Copy Markdown
Author

/approve

@scality scality deleted a comment from bert-e Jul 27, 2026
@bert-e

bert-e commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

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

  • ✔️ development/8.3

The following branches have NOT changed:

  • development/6.4
  • development/7.10
  • development/7.4
  • development/7.70
  • development/8.1
  • development/8.2

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

  • hotfix/7.10.14
  • hotfix/7.4.3
  • hotfix/7.10.0
  • hotfix/7.10.4
  • hotfix/7.4.0
  • hotfix/7.4.8
  • hotfix/7.4.7
  • hotfix/7.10.7
  • hotfix/7.4.2
  • hotfix/7.8.0
  • hotfix/7.4.6
  • hotfix/7.4.4
  • hotfix/6.4.7
  • hotfix/7.4.5
  • hotfix/7.6.0
  • hotfix/7.9.0
  • hotfix/7.10.3
  • hotfix/7.7.0
  • hotfix/7.10.2
  • hotfix/7.10.1
  • hotfix/7.4.10
  • hotfix/7.4.9
  • hotfix/7.4.1
  • hotfix/7.2.0

Please check the status of the associated issue UTAPI-124.

Goodbye maeldonn.

The following options are set: approve

@bert-e
bert-e merged commit 0033485 into development/8.3 Jul 27, 2026
15 checks passed
@bert-e
bert-e deleted the bugfix/UTAPI-124/multi-crr branch July 27, 2026 11:18
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