-
Notifications
You must be signed in to change notification settings - Fork 251
CLDSRV-717: Unify test routeBackbeatForReplication #5919
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CLDSRV-717: Unify test routeBackbeatForReplication #5919
Conversation
The skip will be removed completely by CLDSRV-632
S3C branches used to tests in the same account. There was no Replication account. See: https://github.com/scality/cloudserver/blob/development/7.70/tests/functional/raw-node/test/routes/routeBackbeatForReplication.js
Hello bourgoismickael,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
Request integration branchesWaiting for integration branch creation to be requested by the user. To request integration branches, please comment on this pull request with the following command: Alternatively, the |
❌ 17 Tests Failed:
View the top 3 failed test(s) by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR refactors test code to unify the routeBackbeatForReplication test by introducing support for both same-account and cross-account replication scenarios. The changes eliminate code duplication and make the tests more maintainable.
- Extracts common logic into reusable functions and configuration objects
- Adds scenario-based testing to support both same-account and cross-account replication
- Consolidates repetitive object metadata handling code
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
| objectKey: keyName, | ||
| queryObj: { versionId: 'null' }, | ||
| authCredentials: destinationAuthCredentials, | ||
| authCredentials: sourceAuthCredentials, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why this change? It looks like we are on purpose getting the replicated null version as per the step name
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The bucket is bucketSource, not bucketDestination
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And I get an Access Denied when testing with S3C
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And the PUT into the bucketDestination is done below. If I try a GET on that bucket I get an ObjNotFound.
Now I think maybe we did not get any error in a zenko context because the replication credentials are using the zenko replication service account that can access every resources ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've describe the test phases and renamed the steps to be clearer: 4e067fd
The GET is done on the source to retrieve the object after lifecycle before replicating it to destination.
So the source credentials should be used on the source bucket
Step names were unclear
|
/create_integration_branches |
Integration data createdI have created the integration data for the additional destination branches.
The following branches will NOT be impacted:
You can set option The following options are set: create_integration_branches |
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
The following options are set: create_integration_branches |
|
/approve |
Build failedThe build for commit did not succeed in branch w/9.1/improvement/CLDSRV-717-unify-test-bbreplication The following options are set: approve, create_integration_branches |
In the queueThe changeset has received all authorizations and has been added to the The changeset will be merged in:
The following branches will NOT be impacted:
There is no action required on your side. You will be notified here once IMPORTANT Please do not attempt to modify this pull request.
If you need this pull request to be removed from the queue, please contact a The following options are set: approve, create_integration_branches |
Queue build failedThe corresponding build for the queue failed:
Remove the pull request from the queue
|
|
I have successfully merged the changeset of this pull request
The following branches have NOT changed:
Please check the status of the associated issue CLDSRV-717. Goodbye bourgoismickael. |
Split from #5907 to simplify review
You can review by commit.