SEPURI-SAI-KRISHNA commented on PR #12182: URL: https://github.com/apache/seatunnel/pull/12182#issuecomment-5658369279
Agreed, and that matches what I found independently before reading this. Syncing now. Three notes from the attempt 2 logs. The MinIO failures are wider than `all-connectors-it-7` on this run. Eight legs hit it: `all-connectors-it-2` on `IcebergSourceIT.startUp:161`, `all-connectors-it-6` on `DatabendIT.startUp:249` and `DatabendCDCSinkIT.startUp:221`, `all-connectors-it-7` on `S3FileWithFilterIT.startUp:76`, and `paimon-connector-it` on `PaimonWithS3IT.startUp:151`, each on both JDK legs. That last one means `paimon-connector-it` is no longer the Maven resolution failure. That was attempt 1. On attempt 2 it is the same MinIO pull, so the sync should clear it too. On the registry state, what is observable from outside is that anonymous pulls are denied, rather than that the repository is definitely gone. An anonymous manifest request for `minio/minio` returns 401 UNAUTHORIZED, the same request for `library/alpine` returns 200, and the Hub API reports the repository as not found. The daemon reports that as `404 ... repository does not exist or may require 'docker login'`. The quay mirror is the right fix either way. The comment #12287 adds at the call sites reads the same way, that Docker Hub "no longer serves anonymous/unauthenticated pulls". After the sync I expect `all-connectors-it-7` to stay red on a different MinIO reference. `S3FileConnectDryRunIT` was added by #12242 after #12287 was written and still points at Docker Hub on dev. It is in `connector-file-s3-e2e`, the same module as `S3FileWithFilterIT`, so that leg waits on #12302. The remaining two are unaffected by the sync, as you say: `engine-v2-it` on `BackpressureSlowSinkIT:247` and `SplitClusterFaultToleranceIT:448`, and `transform-v2-it-part-1` on #12116. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
