Zenko icon indicating copy to clipboard operation
Zenko copied to clipboard
verified publisher icon scality

Improvement/zenko 4713 tests on put obj no version

Open benzekrimaha opened this issue 1 year ago • 2 comments

This PR aims to add a test case on the dmfFeature , for the put of an existing object in the cold lolcation in the hot one , in the test we make sure that dmf deletes the already existing object in the cold storage , before the hot location object is transitioned thus avoiding the creation of orphans.

Linked issue : https://scality.atlassian.net/browse/ZENKO-4713

benzekrimaha avatar Jul 02 '24 07:07 benzekrimaha

Hello benzekrimaha,

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 :star:
/bypass_build_status Bypass the build and test status :star:
/bypass_commit_size Bypass the check on the size of the changeset TBA :star:
/bypass_incompatible_branch Bypass the check on the source branch prefix :star:
/bypass_jira_check Bypass the Jira issue check :star:
/bypass_peer_approval Bypass the pull request peers' approval :star:
/bypass_leader_approval Bypass the pull request leaders' approval :star:
/approve Instruct Bert-E that the author has approved the pull request. :writing_hand:
/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 avatar Jul 02 '24 07:07 bert-e

Incorrect fix version

The Fix Version/s in issue ZENKO-4713 contains:

  • None

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

  • 2.7.54

  • 2.8.34

  • 2.9.8

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

bert-e avatar Jul 02 '24 07:07 bert-e

Incorrect fix version

The Fix Version/s in issue ZENKO-4713 contains:

  • None

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

  • 2.7.55

  • 2.8.35

  • 2.9.9

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

bert-e avatar Jul 11 '24 09:07 bert-e

Incorrect fix version

The Fix Version/s in issue ZENKO-4713 contains:

  • None

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

  • 2.10.0

  • 2.7.55

  • 2.8.35

  • 2.9.9

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

bert-e avatar Jul 12 '24 12:07 bert-e

/create_integration_branches

benzekrimaha avatar Jul 18 '24 16:07 benzekrimaha

Integration data created

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

The following branches will NOT be impacted:

  • development/2.5
  • development/2.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: create_integration_branches

bert-e avatar Jul 18 '24 16:07 bert-e

Waiting for approval

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

  • the author

  • 2 peers

The following options are set: create_integration_branches

bert-e avatar Jul 18 '24 16:07 bert-e

@bert-e create_pull_requests

benzekrimaha avatar Jul 18 '24 16:07 benzekrimaha

Integration data created

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

The following branches will NOT be impacted:

  • development/2.5
  • development/2.6

Follow integration pull requests if you would like to be notified of build statuses by email.

The following options are set: create_pull_requests, create_integration_branches

bert-e avatar Jul 18 '24 16:07 bert-e

Waiting for approval

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

  • the author

  • 2 peers

The following options are set: create_pull_requests, create_integration_branches

bert-e avatar Jul 18 '24 16:07 bert-e

/approve

benzekrimaha avatar Jul 18 '24 16:07 benzekrimaha

Build failed

The build for commit did not succeed in branch w/2.8/improvement/ZENKO-4713-tests-on-putObjNoVersion.

The following options are set: approve, create_pull_requests, create_integration_branches

bert-e avatar Jul 18 '24 17:07 bert-e

Build failed

The build for commit did not succeed in branch w/2.9/improvement/ZENKO-4713-tests-on-putObjNoVersion.

The following options are set: approve, create_pull_requests, create_integration_branches

bert-e avatar Jul 19 '24 08:07 bert-e

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:

  • :heavy_check_mark: development/2.7

  • :heavy_check_mark: development/2.8

  • :heavy_check_mark: development/2.9

  • :heavy_check_mark: development/2.10

The following branches will NOT be impacted:

  • development/2.5
  • development/2.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, create_pull_requests, create_integration_branches

bert-e avatar Jul 19 '24 10:07 bert-e

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

  • :heavy_check_mark: development/2.7

  • :heavy_check_mark: development/2.8

  • :heavy_check_mark: development/2.9

  • :heavy_check_mark: development/2.10

The following branches have NOT changed:

  • development/2.5
  • development/2.6

Please check the status of the associated issue ZENKO-4713.

Goodbye benzekrimaha.

bert-e avatar Jul 20 '24 01:07 bert-e