Skip to content

fix site replication status not displayed for crr#5926

Merged
bert-e merged 2 commits intodevelopment/9.1from
improvement/CLDSRV-737
Sep 4, 2025
Merged

fix site replication status not displayed for crr#5926
bert-e merged 2 commits intodevelopment/9.1from
improvement/CLDSRV-737

Conversation

@welansari
Copy link
Copy Markdown

@welansari welansari commented Sep 2, 2025

Replication status of each site is returned as a custom user metadata
when performing a HeadObject. Returning these headers for all location
types.

Issue: CLDSRV-737

@bert-e
Copy link
Copy Markdown
Contributor

bert-e commented Sep 2, 2025

Hello kerkesni,

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.

@codecov
Copy link
Copy Markdown

codecov bot commented Sep 2, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.55%. Comparing base (37b699d) to head (48eb17b).
⚠️ Report is 9 commits behind head on development/9.1.
✅ All tests successful. No failed tests found.

Additional details and impacted files

Impacted file tree graph

Files with missing lines Coverage Δ
lib/utilities/collectResponseHeaders.js 100.00% <100.00%> (+8.92%) ⬆️
@@                 Coverage Diff                 @@
##           development/9.1    #5926      +/-   ##
===================================================
+ Coverage            83.51%   83.55%   +0.04%     
===================================================
  Files                  190      190              
  Lines                12167    12167              
===================================================
+ Hits                 10161    10166       +5     
+ Misses                2006     2001       -5     
Flag Coverage Δ
ceph-backend-test 64.33% <100.00%> (ø)
file-ft-tests 66.19% <100.00%> (+0.03%) ⬆️
kmip-ft-tests 26.96% <0.00%> (ø)
mongo-v0-ft-tests 67.99% <100.00%> (+0.03%) ⬆️
mongo-v1-ft-tests 67.99% <100.00%> (+<0.01%) ⬆️
multiple-backend 34.01% <100.00%> (+0.03%) ⬆️
sur-tests 35.37% <100.00%> (ø)
sur-tests-inflights 36.45% <100.00%> (ø)
unit 68.03% <100.00%> (+0.04%) ⬆️
utapi-v2-tests 33.33% <100.00%> (+<0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@bert-e
Copy link
Copy Markdown
Contributor

bert-e commented Sep 2, 2025

Waiting for approval

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

  • the author

  • 2 peers

@scality scality deleted a comment from bert-e Sep 2, 2025
@welansari welansari force-pushed the improvement/CLDSRV-737 branch from 55733b6 to 3a82af1 Compare September 2, 2025 10:08
@welansari welansari force-pushed the improvement/CLDSRV-737 branch from 3a82af1 to c337210 Compare September 2, 2025 14:32
Comment thread lib/utilities/collectResponseHeaders.js Outdated
@welansari
Copy link
Copy Markdown
Author

/approve

@bert-e
Copy link
Copy Markdown
Contributor

bert-e commented Sep 4, 2025

Build failed

The build for commit did not succeed in branch improvement/CLDSRV-737

The following options are set: approve

Kerkesni added 2 commits September 4, 2025 10:43
Replication status of each site is returned as a custom user metadata
when performing a HeadObject. Returning these headers for all location
types.

Issue: CLDSRV-737
@welansari welansari force-pushed the improvement/CLDSRV-737 branch from 7c8ecaa to 48eb17b Compare September 4, 2025 08:43
@bert-e
Copy link
Copy Markdown
Contributor

bert-e commented Sep 4, 2025

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.1

The following branches will NOT be impacted:

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

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
Copy link
Copy Markdown
Contributor

bert-e commented Sep 4, 2025

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

  • ✔️ development/9.1

The following branches have NOT changed:

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

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

Goodbye kerkesni.

@bert-e bert-e merged commit 211296a into development/9.1 Sep 4, 2025
52 of 53 checks passed
@bert-e bert-e deleted the improvement/CLDSRV-737 branch September 4, 2025 09:30
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.

4 participants