-
Notifications
You must be signed in to change notification settings - Fork 242
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
fix(image): use latest lts
instead of fixed
version
#5550
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…gfix/CLDSRV-412/null
…o w/8.8/improvement/CLDSRV-414/bump
… tmp/octopus/w/8.8/improvement/CLDSRV-411-impose-last-modified
… tmp/octopus/w/8.8/improvement/CLDSRV-411-impose-last-modified
… tmp/octopus/w/8.8/improvement/CLDSRV-411-impose-last-modified
… tmp/octopus/w/8.8/improvement/CLDSRV-411-impose-last-modified
…o tmp/octopus/w/8.8/bugfix/CLDSRV-418/CLDSRV_196_backport_to_710
…nd 'q/5243/8.7/bugfix/CLDSRV-418/CLDSRV_196_backport_to_710' into tmp/octopus/q/8.8
…ment/CLDSRV-400' into tmp/octopus/q/8.8
…ata-getting-deleted-when-restoring' into w/8.8/improvement/CLDSRV-408-Fix-metadata-getting-deleted-when-restoring
… tmp/octopus/w/8.8/bugfix/CLDSRV-413/crr_existing_null_version
….8/feature/CLDSRV-420/backport
…ature/CLDSRV-420/backport' into tmp/octopus/q/8.8
…sion' into w/8.8/bugfix/CLDSRV-413/bump_version
…mp/octopus/w/8.8/bugfix/CLDSRV-439/bump_arsenal_for_bugfix
This tests for SPRXCLT-12 issue
They had been disabled for a long while and cannot be reenabled yet because they don't pass, so keep on skipping them for now. Tickets have been created to take care of them: - CLDSRV-440 - CLDSRV-441 - CLDSRV-442 - CLDSRV-443
…topus/w/8.8/bugfix/CLDSRV-444-id-resource-policy
Issue: CLDSRV-570
When an objects overwrites an object in a non-versioned bucket, need to add special handling to ensure an oplog entry is generated about the "removal" of object: so that Backbeat can detect it, and notify cold storage backend. This was fixed already for putObject in CLDSRV-560, but the MPU and copyObject cases were not handled. Issue: CLDSRV-577
Issue: CLDSRV-577
…8/bugfix/CLDSRV-580/aws_kms0
Previously, we were dynamically calling the internal authorization API to check if the identity, when not an account, has the permission to bypass the governance lock configuration. This call sent request contexts with information we already have when authorizing the API, except the type of identity. This commit introduces an optimization by including the Bypass action, when the header is set, directly when the api is authorized. If the identity is an account, the overhead is lower than doing another API call: no policy are evaluated. Both PutObjectRetention and DeleteObject API calls are updated accordingly.
Issue: CLDSRV-583
…octopus/w/8.8/improvement/CLDSRV-574/kms-healthcheck
… tmp/octopus/w/8.8/improvement/CLDSRV-574/kms-healthcheck-7.70
- Previously the inflights returned by scuba would not be below 0 - After a metrics update, it may take some time to get new metrics - In this case, if inflights are at 0, we end up in a blocked situation, as deleting data won't reduce the usage and thus the quota may block operations for hours. Issue: CLDSRV-587
…ctopus/w/8.8/bugfix/CLDSRV-571-better-handling-of-errors
…d 'q/w/5692/8.7/bugfix/CLDSRV-571-better-handling-of-errors' into tmp/octopus/q/8.8
Issue: CLDSRV-563
- Backbeat may send internal API requests that will evaluate quotas. This change fixes these scenarios, as they were trying to push finalizer hooks to an empty object. Issue: CLDSRV-586
Issue: CLDSRV-586
The route backbeat also calls the doAuth function, but we never map the value to accountQuotas Issue: CLDSRV-590
From backbeat routes, all APIs will use a name we only need for monitoring, but the action name is actually used during the quota evalutation (and possibly bucket policy as well). Issue: CLDSRV-590
This is needed to track deletions in case of transition or restored object expiration. Issue: CLDSRV-590
BB routes are not authorizing internal API calls. To be adressed in CLDSRV-591 Issue: CLDSRV-590
Deleting cold objects should not increment inflight, unless they are restored. Issue: CLDSRV-590
Issue: CLDSRV-590
Issue: CLDSRV-590
Issue: CLDSRV-590
Issue: CLDSRV-594
Issue: CLDSRV-594
Issue: CLDSRV-594
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull request template
Description
Motivation and context
This PR may fix #5549 and expand architecture/platforms
Related issues
#5549
Checklist
Add tests to cover the changes
New tests added or existing tests modified to cover all changes
Code conforms with the style guide
Sign your work
In order to contribute to the project, you must sign your work
https://github.com/scality/Guidelines/blob/master/CONTRIBUTING.md#sign-your-work
Thank you again for contributing! We will try to test and integrate the change
as soon as we can.