-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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 SSEC multipart checksum replication #19915
Fix SSEC multipart checksum replication #19915
Conversation
* Multipart SSEC checksums were not transferred. * Remove key mismatch logging. This key is user controlled with SSEC. * If source is SSEC and destination reports ErrSSEEncryptedObject, assume replication is good.
your PR made me realize CopyObject SSE-C replication is broken - klauspost#6 is needed in addition to your changes for SSEC replication. would be good to consolidate this change in the same PR |
@harshavardhana Did you re-run the "upgrade" as well? If so, it may be triggered by something in the proposal from @poornas If it fails again, let's revert and debug it separately. |
Some how recreating the same container images is failing |
it looks like something changed in the GitHub runner environment, testing it with other PRs. |
Okay so this is broken in all PRs, will disable the upgrade tests for now. |
merged #19926 should fix the build issue. |
Description
How to test this PR?
Upload multipart with SSE-C and checksum (used a modified mc)
Verify that the replica has checksum. Again, modified mc:
Note replica has
X-Amz-Checksum-Crc32c
as expected and it is decoded correctly with provided SSEC key.Types of changes