Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
1.16.0, 1.17.0, 1.15.3
-
None
Description
There are two build failures (branch based on release-1.16 and a release-1.15 build) that are (not exclusively) caused by the e2e test Kubernetes test failing in the initialization phase (i.e. when installing all artifacts):
See the attached logs from the release-1.15 build's CI output. No logs are present as artifacts.
UPDATE: The error we're seeing is actually FLINK-28269 because we failed to download crictl. Looks like we reached some download limit:
2022-10-16T05:58:33.0821044Z --2022-10-16 05:58:33-- https://objects.githubusercontent.com/github-production-release-asset-2e65be/80172100/7186c302-3766-4ed5-920a-f85c9d6334ac?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20221016%2Fus-east-1%2Fs3%2Faws4
_request&X-Amz-Date=20221016T055833Z&X-Amz-Expires=300&X-Amz-Signature=5c24f88d9891e793000a904879be5e8913d643cbff1bfdfb8d0cf3c6e7a7908b&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=80172100&response-content-disposition=attachment%3B%20filename%3Dcrictl-v1.24.2-linux-amd64.t
ar.gz&response-content-type=application%2Foctet-stream
2022-10-16T05:58:33.1021704Z Resolving objects.githubusercontent.com (objects.githubusercontent.com)... 185.199.108.133, 185.199.111.133, 185.199.110.133, ...
2022-10-16T05:58:33.1128247Z Connecting to objects.githubusercontent.com (objects.githubusercontent.com)|185.199.108.133|:443... connected.
2022-10-16T05:58:38.5605126Z HTTP request sent, awaiting response... 503 Egress is over the account limit.
2022-10-16T05:58:38.5606342Z 2022-10-16 05:58:38 ERROR 503: Egress is over the account limit..
Attachments
Attachments
Issue Links
- is duplicated by
-
FLINK-30178 Kubernetes test failed with "crictl: command not found"
- Closed
- is related to
-
FLINK-32107 Kubernetes test failed because ofunable to establish ssl connection to github on AZP
- Resolved
-
FLINK-28269 Kubernetes test failed with permission denied
- Closed
- relates to
-
FLINK-30881 Crictl/Minikube version mismatch causes errors in k8s setup
- Resolved
-
FLINK-30893 Replace not specifying a driver in Minikube by something else
- Open