investigate intermettant CI unit test failures

[kevinjqliu]

Apache Iceberg Rust version

None

Describe the bug

I've seen this several times, and usually rerun will work

For example,
https://github.com/apache/iceberg-rust/actions/runs/19275372364/job/55113753177?pr=1836

failures:

---- test_create_table stdout ----
Error: Unexpected => Failure in doing io operation

Source: ConfigInvalid (persistent) at write, context: { uri: http://172.18.0.3:9000/warehouse/hive/metadata/00000-073ab8a0-e0c1-48ee-88bb-a8f5a23e0bb0.metadata.json, response: Parts { status: 404, version: HTTP/1.1, headers: {"accept-ranges": "bytes", "content-length": "470", "content-type": "application/xml", "server": "MinIO", "strict-transport-security": "max-age=31536000; includeSubDomains", "vary": "Origin", "vary": "Accept-Encoding", "x-amz-id-2": "dd9025bab4ad464b049177c95eb6ebf374d3b3fd1af9251148b658df7ac2e3e8", "x-amz-request-id": "187708804D4641F6", "x-content-type-options": "nosniff", "x-ratelimit-limit": "4237", "x-ratelimit-remaining": "4237", "x-xss-protection": "1; mode=block", "date": "Tue, 11 Nov 2025 18:52:06 GMT"} }, service: s3, path: hive/metadata/00000-073ab8a0-e0c1-48ee-88bb-a8f5a23e0bb0.metadata.json, written: 533 } => S3Error { code: "NoSuchBucket", message: "The specified bucket does not exist", resource: "/warehouse/hive/metadata/00000-073ab8a0-e0c1-48ee-88bb-a8f5a23e0bb0.metadata.json", request_id: "187708804D4641F6" }


---- test_drop_table stdout ----
Error: Unexpected => Failure in doing io operation

Source: ConfigInvalid (persistent) at write, context: { uri: http://172.18.0.3:9000/warehouse/hive/test_drop_table.db/my_table/metadata/00000-e9f6bb18-0428-4840-86b6-c25f1fa661a6.metadata.json, response: Parts { status: 404, version: HTTP/1.1, headers: {"accept-ranges": "bytes", "content-length": "526", "content-type": "application/xml", "server": "MinIO", "strict-transport-security": "max-age=31536000; includeSubDomains", "vary": "Origin", "vary": "Accept-Encoding", "x-amz-id-2": "dd9025bab4ad464b049177c95eb6ebf374d3b3fd1af9251148b658df7ac2e3e8", "x-amz-request-id": "187708804DD4E4A9", "x-content-type-options": "nosniff", "x-ratelimit-limit": "4237", "x-ratelimit-remaining": "4237", "x-xss-protection": "1; mode=block", "date": "Tue, 11 Nov 2025 18:52:06 GMT"} }, service: s3, path: hive/test_drop_table.db/my_table/metadata/00000-e9f6bb18-0428-4840-86b6-c25f1fa661a6.metadata.json, written: 561 } => S3Error { code: "NoSuchBucket", message: "The specified bucket does not exist", resource: "/warehouse/hive/test_drop_table.db/my_table/metadata/00000-e9f6bb18-0428-4840-86b6-c25f1fa661a6.metadata.json", request_id: "187708804DD4E4A9" }



failures:
    test_create_table
    test_drop_table

test result: FAILED. 12 passed; 2 failed; 0 ignored; 0 measured; 0 filtered out; finished in 1.65s

...


error: 1 target failed:
    `-p iceberg-catalog-glue --test glue_catalog_test`
Error: Process completed with exit code 101.

To Reproduce

No response

Expected behavior

No response

Willingness to contribute

None

[liurenjie1024]

Is there similar problem in pyiceberg? It seems that the unstability is from minio. We are currently starting several docker composes set using rust code, which prevents us from using nextest.