)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":13425,"name":"Simon Dodsley","email":"simon@everpuredata.com","username":"sdodsley"},"change_message_id":"a4d69394b6bd261c0a17c4191c6b17a8f4877b7e","unresolved":true,"context_lines":[{"line_number":9,"context_line":"There is no need for it and we already doing sha256 checksums"},{"line_number":10,"context_line":"for every chunk(for incremental backups)."},{"line_number":11,"context_line":""},{"line_number":12,"context_line":"Closes-Bug: #2142032"},{"line_number":13,"context_line":"Change-Id: I0790c339637f4979b886f71899d811ea5062887a"},{"line_number":14,"context_line":"Signed-off-by: Max Lamprecht \u003cmax.lamprecht@stackit.cloud\u003e"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":2,"id":"35f3703a_b04fc820","line":12,"updated":"2026-10-26 14:37:53.000000000","message":"Please also add `Related-Bug: #2093181`. That bug asks why the backup drivers use MD5 at all, and 941473 proposes making this same hash configurable between MD5 and xxHash. This change answers the question by removing the hash and edits the same lines as 941473, so the link lets that change be closed out once this merges.","commit_id":"55dd235965101946b945064842ca960507f352f1"}],"/PATCHSET_LEVEL":[{"author":{"_account_id":13425,"name":"Simon Dodsley","email":"simon@everpuredata.com","username":"sdodsley"},"change_message_id":"d3c111534b94fdc47b2fedf88f7569f4baa5436d","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"ad1c2e05_3d796292","updated":"2026-10-26 13:19:40.000000000","message":"This would be a +1, but it needs a rebase, so -1 until that is done.","commit_id":"c010a457ff9678873faede075c5d02e3442a3e14"},{"author":{"_account_id":35676,"name":"Max","email":"max.lamprecht@digits.schwarz","username":"lamprechtm"},"change_message_id":"37e58ca72046180e4ce43d072a560662d5c78b32","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"f185a170_1571b737","updated":"2026-02-25 16:35:48.000000000","message":"recheck - devstack-plugin-nfs-tempest-full CI timeout","commit_id":"c010a457ff9678873faede075c5d02e3442a3e14"},{"author":{"_account_id":35676,"name":"Max","email":"max.lamprecht@digits.schwarz","username":"lamprechtm"},"change_message_id":"83e1ad3a3c7ab462e1b7c682013cf82b43d1450f","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"2a2d0103_42d269a5","in_reply_to":"ad1c2e05_3d796292","updated":"2026-10-26 14:23:38.000000000","message":"rebased","commit_id":"c010a457ff9678873faede075c5d02e3442a3e14"},{"author":{"_account_id":13425,"name":"Simon Dodsley","email":"simon@everpuredata.com","username":"sdodsley"},"change_message_id":"a4d69394b6bd261c0a17c4191c6b17a8f4877b7e","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"4828a23f_99fdea88","updated":"2026-10-26 14:37:53.000000000","message":"Two follow-ups, neither blocking:\n\n1. Please add a release note, since new chunked backups no longer contain `md5` in their metadata and tools that read the metadata object may notice. Suggested text, under upgrade: \"The chunked backup drivers no longer record an MD5 checksum for each backup object in the backup metadata. Cinder never read this value, and the Swift, S3 and Google Cloud Storage drivers still verify every upload with their own checksum. Removing it saves a full hash pass over every chunk (`Bug #2142032 \u003chttps://bugs.launchpad.net/cinder/+bug/2142032\u003e_`).\"\n2. `cinder/tests/unit/backup/drivers/test_backup_nfs.py` still defines `fake_md5()` (lines 178-181) and mocks `hashlib.md5` in `setUp` (line 236). After this change no NFS or POSIX code path calls MD5, so the helper, the mock and the then-unused `import hashlib` (line 19) can go in this change. The Swift test module has its own copy, which is still needed.","commit_id":"55dd235965101946b945064842ca960507f352f1"}]}