Skip to content
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

LifecycleDeleteObjectTask: BackbeatRoutes in S3C do not support non versioned buckets #2541

Conversation

benzekrimaha
Copy link
Contributor

@benzekrimaha benzekrimaha commented Sep 19, 2024

Issue : BB-555

@bert-e
Copy link
Contributor

bert-e commented Sep 19, 2024

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

Copy link

codecov bot commented Sep 19, 2024

Codecov Report

Attention: Patch coverage is 80.00000% with 1 line in your changes missing coverage. Please review.

Project coverage is 69.79%. Comparing base (d19fbd5) to head (4b195cc).
Report is 1 commits behind head on development/8.7.

Files with missing lines Patch % Lines
lib/BackbeatMetadataProxy.js 0.00% 1 Missing ⚠️
Additional details and impacted files

Impacted file tree graph

Files with missing lines Coverage Δ
...sions/lifecycle/tasks/LifecycleDeleteObjectTask.js 90.83% <100.00%> (+1.77%) ⬆️
lib/BackbeatMetadataProxy.js 50.00% <0.00%> (ø)

... and 2 files with indirect coverage changes

Components Coverage Δ
Bucket Notification 66.66% <ø> (ø)
Core Library 74.18% <0.00%> (-0.21%) ⬇️
Ingestion 69.24% <ø> (ø)
Lifecycle 75.92% <100.00%> (+0.09%) ⬆️
Oplog Populator 82.95% <ø> (ø)
Replication 57.42% <ø> (ø)
Bucket Scanner 85.60% <ø> (ø)
@@                 Coverage Diff                 @@
##           development/8.7    #2541      +/-   ##
===================================================
- Coverage            69.86%   69.79%   -0.07%     
===================================================
  Files                  194      194              
  Lines                12897    12900       +3     
===================================================
- Hits                  9010     9004       -6     
- Misses                3877     3886       +9     
  Partials                10       10              
Flag Coverage Δ
api:retry 9.65% <0.00%> (-0.01%) ⬇️
api:routes 9.54% <0.00%> (-0.01%) ⬇️
bucket-scanner 85.60% <ø> (ø)
ingestion 12.47% <0.00%> (-0.01%) ⬇️
lib 7.52% <0.00%> (-0.01%) ⬇️
lifecycle 19.34% <0.00%> (+0.01%) ⬆️
notification 0.88% <0.00%> (-0.01%) ⬇️
replication 18.90% <0.00%> (-0.10%) ⬇️
unit 44.88% <80.00%> (+0.02%) ⬆️

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

@benzekrimaha benzekrimaha changed the title BB-462 Expiring non-versioned objects fails LifecycleDeleteObjectTask: BackbeatRoutes in S3C do not support non versioned objects Sep 19, 2024
@benzekrimaha benzekrimaha force-pushed the improvement/BB-555-handle-cldsrv-not-supporting-non-versioned-objects branch from c566e77 to 4d15eb9 Compare September 19, 2024 13:24
@bert-e
Copy link
Contributor

bert-e commented Sep 19, 2024

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 19, 2024
@benzekrimaha benzekrimaha marked this pull request as ready for review September 20, 2024 12:31
@benzekrimaha benzekrimaha force-pushed the improvement/BB-555-handle-cldsrv-not-supporting-non-versioned-objects branch from 3711e92 to 36feb68 Compare September 20, 2024 12:32
// <!> Only in S3C <!> Backbeat API returns 'InvalidBucketState' error if the bucket is not versioned.
// In this case, instead of logging an error, it should be logged as a debug message,
// to avoid causing unnecessary concern to the customer.
// TODO: After the implementation of CLDSRV-461, we could remove this check.
Copy link
Contributor

Choose a reason for hiding this comment

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

Let's have a ticket number with the TODO 🙂

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@benzekrimaha benzekrimaha changed the title LifecycleDeleteObjectTask: BackbeatRoutes in S3C do not support non versioned objects LifecycleDeleteObjectTask: BackbeatRoutes in S3C do not support non versioned buckets Oct 8, 2024
@benzekrimaha benzekrimaha force-pushed the improvement/BB-555-handle-cldsrv-not-supporting-non-versioned-objects branch 2 times, most recently from f1d8504 to 6b57c7c Compare October 15, 2024 05:55
@benzekrimaha benzekrimaha force-pushed the improvement/BB-555-handle-cldsrv-not-supporting-non-versioned-objects branch from 95adf7d to e7ab515 Compare October 15, 2024 10:00
tests/unit/mocks.js Outdated Show resolved Hide resolved
@benzekrimaha benzekrimaha force-pushed the improvement/BB-555-handle-cldsrv-not-supporting-non-versioned-objects branch from 58c4f4c to 455cb94 Compare October 18, 2024 13:54
Note: Only buckets with versioning enabled can be configured for replication.

To expire non-versioned objects correctly, we currently rely on the InvalidBucketState error returned when the S3C Backbeat API is used for a non-versioned bucket's object, until CLDSRV-461 is implemented to add support for non-versioned buckets to the Backbeat API.

Issue : BB-555
@benzekrimaha benzekrimaha force-pushed the improvement/BB-555-handle-cldsrv-not-supporting-non-versioned-objects branch from 455cb94 to 4b195cc Compare October 18, 2024 13:55
@benzekrimaha
Copy link
Contributor Author

/approve

@bert-e
Copy link
Contributor

bert-e commented Oct 18, 2024

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

  • ✔️ development/8.7

The following branches have NOT changed:

  • development/7.10
  • development/7.4
  • development/7.70
  • development/8.5
  • development/8.6

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

Goodbye benzekrimaha.

The following options are set: approve

@bert-e bert-e merged commit 4b195cc into development/8.7 Oct 18, 2024
9 checks passed
@bert-e bert-e deleted the improvement/BB-555-handle-cldsrv-not-supporting-non-versioned-objects branch October 18, 2024 14:27
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