BB-744 Fix V4 signature using proxyPath instead of original path by nicolas2bert · Pull Request #2717 · scality/backbeat

nicolas2bert · 2026-02-17T09:17:28Z

Bump vaultclient to add scality/vaultclient#463

bert-e · 2026-02-17T09:17:32Z

Hello nicolas2bert,

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 · 2026-02-17T09:17:36Z

Incorrect fix version

The Fix Version/s in issue BB-744 contains:

None

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

9.0.25
9.1.8
9.2.1
9.3.0

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

codecov · 2026-02-17T09:17:54Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 74.09%. Comparing base (ccacdb7) to head (147adb2).
⚠️ Report is 4 commits behind head on development/9.0.

Additional details and impacted files

see 3 files with indirect coverage changes

Components	Coverage Δ
Bucket Notification	`80.35% <ø> (ø)`
Core Library	`80.38% <ø> (-0.60%)`	⬇️
Ingestion	`70.81% <ø> (ø)`
Lifecycle	`78.67% <ø> (ø)`
Oplog Populator	`85.06% <ø> (ø)`
Replication	`58.48% <ø> (ø)`
Bucket Scanner	`85.76% <ø> (ø)`

@@                 Coverage Diff                 @@
##           development/9.0    #2717      +/-   ##
===================================================
- Coverage            74.33%   74.09%   -0.25%     
===================================================
  Files                  202      202              
  Lines                13478    13478              
===================================================
- Hits                 10019     9986      -33     
- Misses                3449     3482      +33     
  Partials                10       10

Flag	Coverage Δ
api:retry	`9.46% <ø> (ø)`
api:routes	`9.27% <ø> (ø)`
bucket-scanner	`85.76% <ø> (ø)`
ft_test:queuepopulator	`8.92% <ø> (-1.29%)`	⬇️
ingestion	`12.56% <ø> (ø)`
lib	`7.47% <ø> (-0.01%)`	⬇️
lifecycle	`18.66% <ø> (ø)`
notification	`1.04% <ø> (ø)`
replication	`18.55% <ø> (ø)`
unit	`50.03% <ø> (ø)`

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

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

yarn.lock

nicolas2bert · 2026-02-17T14:24:25Z

@bert-e approve

bert-e · 2026-02-17T14:24:33Z

Incorrect fix version

The Fix Version/s in issue BB-744 contains:

None

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

9.0.25
9.1.8
9.2.1
9.3.0

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

The following options are set: approve

bert-e · 2026-02-17T14:28:47Z

Conflict

A conflict has been raised during the creation of
integration branch w/9.1/bugfix/BB-744/signature with contents from bugfix/BB-744/signature
and development/9.1.

I have not created the integration branch.

Here are the steps to resolve this conflict:

 git fetch
 git checkout -B w/9.1/bugfix/BB-744/signature origin/development/9.1
 git merge origin/bugfix/BB-744/signature
 # <intense conflict resolution>
 git commit
 git push -u origin w/9.1/bugfix/BB-744/signature

The following options are set: approve

bert-e · 2026-02-17T14:37:28Z

Conflict

A conflict has been raised during the creation of
integration branch w/9.2/bugfix/BB-744/signature with contents from w/9.1/bugfix/BB-744/signature
and development/9.2.

I have not created the integration branch.

Here are the steps to resolve this conflict:

 git fetch
 git checkout -B w/9.2/bugfix/BB-744/signature origin/development/9.2
 git merge origin/w/9.1/bugfix/BB-744/signature
 # <intense conflict resolution>
 git commit
 git push -u origin w/9.2/bugfix/BB-744/signature

The following options are set: approve

bert-e · 2026-02-17T14:47:43Z

Integration data created

I have created the integration data for the additional destination branches.

this pull request will merge bugfix/BB-744/signature into
development/9.0
w/9.1/bugfix/BB-744/signature will be merged into development/9.1
w/9.2/bugfix/BB-744/signature will be merged into development/9.2
w/9.3/bugfix/BB-744/signature will be merged into development/9.3

The following branches will NOT be impacted:

development/7.10
development/7.4
development/7.70
development/8.6

You can set option create_pull_requests if you need me to create
integration pull requests in addition to integration branches, with:

@bert-e create_pull_requests

The following options are set: approve

bert-e · 2026-02-17T15:13:46Z

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.0
✔️ development/9.1
✔️ development/9.2
✔️ development/9.3

The following branches will NOT be impacted:

development/7.10
development/7.4
development/7.70
development/8.6

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 · 2026-02-17T15:34:51Z

Queue build failed

The corresponding build for the queue failed:

Checkout the status page.
Identify the failing build and review the logs.
If no issue is found, re-run the build.
If an issue is identified, checkout the steps below to remove
the pull request from the queue for further analysis and maybe rebase/merge.

Remove the pull request from the queue

Add a /wait comment on this pull request.
Click on login on the status page.
Go into the manage page.
Find the option called Rebuild the queue and click on it.
Bert-E will loop again on all pull requests to put the valid ones
in the queue again, while skipping the one with the /wait comment.
Wait for the new queue to merge, then merge/rebase your pull request
with the latest changes to then work on a proper fix.
Once the issue is fixed, delete the /wait comment and
follow the usual process to merge the pull request.

bert-e · 2026-02-17T16:57:06Z

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.0
✔️ development/9.1
✔️ development/9.2
✔️ development/9.3

The following branches will NOT be impacted:

development/7.10
development/7.4
development/7.70
development/8.6

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 · 2026-02-17T17:35:52Z

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

✔️ development/9.0
✔️ development/9.1
✔️ development/9.2
✔️ development/9.3

The following branches have NOT changed:

development/7.10
development/7.4
development/7.70
development/8.6

Please check the status of the associated issue BB-744.

Goodbye nicolas2bert.

BB-744 Fix V4 signature using proxyPath instead of original path

3b17783

fredmnl approved these changes Feb 17, 2026

View reviewed changes

anurag4DSB approved these changes Feb 17, 2026

View reviewed changes

BourgoisMickael reviewed Feb 17, 2026

View reviewed changes

yarn.lock Show resolved Hide resolved

BourgoisMickael approved these changes Feb 17, 2026

View reviewed changes

BB-744 bump backbeat version

147adb2

bert-e merged commit a8aa912 into development/9.0 Feb 17, 2026
10 checks passed

bert-e deleted the bugfix/BB-744/signature branch February 17, 2026 17:35

Conversation

nicolas2bert commented Feb 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

bert-e commented Feb 17, 2026

Hello nicolas2bert,

Uh oh!

bert-e commented Feb 17, 2026

Incorrect fix version

Uh oh!

codecov bot commented Feb 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

Uh oh!

nicolas2bert commented Feb 17, 2026

Uh oh!

bert-e commented Feb 17, 2026

Incorrect fix version

Uh oh!

bert-e commented Feb 17, 2026

Conflict

Uh oh!

bert-e commented Feb 17, 2026

Conflict

Uh oh!

bert-e commented Feb 17, 2026

Integration data created

Uh oh!

bert-e commented Feb 17, 2026

In the queue

Uh oh!

bert-e commented Feb 17, 2026

Queue build failed

Uh oh!

bert-e commented Feb 17, 2026

In the queue

Uh oh!

bert-e commented Feb 17, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

Comments

nicolas2bert commented Feb 17, 2026 •

edited

Loading

codecov bot commented Feb 17, 2026 •

edited

Loading