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

backupccl: disabling S3DisableContentMD5Validation causes uploads to object locked buckets to fail #115602

Closed
adityamaru opened this issue Dec 5, 2023 · 2 comments
Assignees
Labels
A-disaster-recovery branch-release-23.1 Used to mark GA and release blockers, technical advisories, and bugs for 23.1 branch-release-23.2 Used to mark GA and release blockers, technical advisories, and bugs for 23.2 C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. O-support Would prevent or help troubleshoot a customer escalation - bugs, missing observability/tooling, docs P-0 Issues/test failures with a fix SLA of 2 weeks T-disaster-recovery

Comments

@adityamaru
Copy link
Contributor

adityamaru commented Dec 5, 2023

In #115197 we introduced a regression where uploads to object locked buckets will fail as they require S3DisableContentMD5Validation to be set to false. The error is of the form closing object: upload failed: InvalidRequest: Content-MD5 OR x-amz-checksum- HTTP header is required for Put Object requests with Object Lock parameters. This issue tracks the revert and follow up fixes to this regression. The regression is in unreleased code and so there is no customer impact.

As part of resolving this release blocker we should write a regression test that runs a backup to an object lock bucket to ensure that something fails were this change to be made in the future.

Jira issue: CRDB-34120

@adityamaru adityamaru added C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. T-disaster-recovery branch-release-23.1 Used to mark GA and release blockers, technical advisories, and bugs for 23.1 branch-release-23.2 Used to mark GA and release blockers, technical advisories, and bugs for 23.2 labels Dec 5, 2023
Copy link

blathers-crl bot commented Dec 5, 2023

cc @cockroachdb/disaster-recovery

@adityamaru adityamaru self-assigned this Dec 5, 2023
@adityamaru adityamaru removed the release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. label Dec 6, 2023
craig bot pushed a commit that referenced this issue Dec 6, 2023
115671: storage: populate OmitInRangefeeds in MVCC code r=RaduBerinde a=RaduBerinde

This change populates the `MVCCValueHEader.OmitInRangeFeeds` flag based on the corresponding flag in the transaction.

Fixes: #113634
Release note: None

115707: sql: prevent creating indexes on arrays of non-indexable types r=DrewKimball,fqazi,rafiss a=chrisseto

#### ae7fbfb sql: prevent creating indexes on arrays of non-indexable types

Previously, it was possible to circumvent the check performed by
`ColumnTypeIsIndexable` and `ColumnTypeIsInvertedIndexable` by wrapping
a type in an array. Doing so would violate some invariants across the
system and lead to undefined behavior.

This commit updates both `ColumnTypeIsIndexable` and
`ColumnTypeIsInvertedIndexable` to unwrap array types, as necessary, to
prevent invalid indexes from being created.

Fixes: #115701
Epic: none
Release note (bug fix): Standard and inverted indexes may no longer be
created on REFCURSOR[]s columns. REFCURSOR columns themselves are not
indexable.

115713: Revert "s3: disable content pre-upload checksums" r=stevendanna a=adityamaru

This reverts commit 50c453a.

Release note (bug fix): fixes a regression that causes uploads to object locked buckets to fail because of the absence of an MD5 hash

Informs: #115602

Co-authored-by: Radu Berinde <[email protected]>
Co-authored-by: Chris Seto <[email protected]>
Co-authored-by: adityamaru <[email protected]>
@adityamaru
Copy link
Contributor Author

This has been reverted on all branches and a regression test has been added.

@shralex shralex added the O-support Would prevent or help troubleshoot a customer escalation - bugs, missing observability/tooling, docs label Dec 11, 2023
@benbardin benbardin added the P-0 Issues/test failures with a fix SLA of 2 weeks label Dec 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-disaster-recovery branch-release-23.1 Used to mark GA and release blockers, technical advisories, and bugs for 23.1 branch-release-23.2 Used to mark GA and release blockers, technical advisories, and bugs for 23.2 C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. O-support Would prevent or help troubleshoot a customer escalation - bugs, missing observability/tooling, docs P-0 Issues/test failures with a fix SLA of 2 weeks T-disaster-recovery
Projects
No open projects
Archived in project
Development

No branches or pull requests

3 participants