@qoega, the images updated successfully, and the integration tests work, but there were many failures after we disabled retries. If this is only related to retries, let's merge.

Lets dig

Integration tests (asan) [1/6]

• test_allowed_url_from_config LeakSanitizer: detected memory leaks OPENSSL_malloc build_docker/../contrib/boringssl/crypto/mem.c:139:15 #44928
• test_broken_detached_part_clean_up/test.py::test_store_cleanup Logical error: New empty part is about to matirialize but the dirrectory already exist #43735

Integration tests (asan) [2/6] — fail: 2, passed: 248, flaky: 3

• test_merge_tree_s3_restore LeakSanitizer: detected memory leaks OPENSSL_malloc build_docker/../contrib/boringssl/crypto/mem.c:139:15 #44928
• test_keeper_snapshot_on_exit Avoid Keeper crash on shutdown (fix test_keeper_snapshot_on_exit) #44908
• test_join_set_family_s3 LeakSanitizer: detected memory leaks OPENSSL_malloc build_docker/../contrib/boringssl/crypto/mem.c:139:15 #44928
• test_storage_hudi LeakSanitizer: detected memory leaks OPENSSL_malloc build_docker/../contrib/boringssl/crypto/mem.c:139:15 #44928

Integration tests (asan) [4/6] — fail: 32, passed: 238, flaky: 2

• test_storage_rabbitmq Try fix rabbitmq potential leak #44897
• test_replicated_merge_tree_s3_restore LeakSanitizer: detected memory leaks OPENSSL_malloc build_docker/../contrib/boringssl/crypto/mem.c:139:15 #44928
• test_s3_cluster LeakSanitizer: detected memory leaks OPENSSL_malloc build_docker/../contrib/boringssl/crypto/mem.c:139:15 #44928

Integration tests (asan) [5/6] — fail: 1, passed: 465, flaky: 2

• test_backup_restore_on_cluster Flaky test test_backup_restore_on_cluster/test_concurrency.py #42719
• test_storage_delta LeakSanitizer: detected memory leaks OPENSSL_malloc build_docker/../contrib/boringssl/crypto/mem.c:139:15 #44928
• test_storage_s3 LeakSanitizer: detected memory leaks OPENSSL_malloc build_docker/../contrib/boringssl/crypto/mem.c:139:15 #44928

Integration tests (asan) [6/6] — fail: 2, passed: 388, flaky: 2

• test_azure_blob_storage_zero_copy_replication LeakSanitizer: detected memory leaks azurite #44862
• test_backup_restore_new Flaky test_backup_restore_new #44901
  Integration tests (release) [1/4] — fail: 1, passed: 570, flaky: 0
• test_backup_restore_on_cluster Flaky test test_backup_restore_on_cluster/test_concurrency.py #42719
  Integration tests (release) [2/4] — fail: 9, passed: 541, flaky: 2
• test_backup_restore_new Flaky test_backup_restore_new #44901
• test_s3_zero_copy_ttl is flaky the way it is written. Probably we need to remove it

        # 3G limit is a big one. However, we can hit it anyway with parallel s3 writes enabled.
        # Also actual value can be bigger because of memory drift.
        # Increase it a little bit if test fails.
>       assert int(max_usage) < 3e9
E       AssertionError: assert 3356058560 < 3000000000.0
E        +  where 3356058560 = int('3356058560\n')

Integration tests (release) [3/4] — fail: 1, passed: 461, flaky: 0

• test_broken_detached_part_clean_up Logical error: New empty part is about to matirialize but the dirrectory already exist #43735

Integration tests (release) [4/4] — fail: 1, passed: 354, flaky: 0

• test_keeper_snapshot_on_exit/test.py::test_snapshot_on_exit Avoid Keeper crash on shutdown (fix test_keeper_snapshot_on_exit) #44908

Integration tests (tsan)

• test_broken_detached_part_clean_up Logical error: New empty part is about to matirialize but the dirrectory already exist #43735
• test_keeper_snapshot_on_exit/test.py::test_snapshot_on_exit Avoid Keeper crash on shutdown (fix test_keeper_snapshot_on_exit) #44908
• test_backup_restore_on_cluster Flaky test_backup_restore_new #44901
• test_backup_restore_new Flaky test_backup_restore_new #44901
• test_replicated_users new test_replicated_users flaky #44932