[ 
https://issues.apache.org/jira/browse/FLINK-29671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17683293#comment-17683293
 ] 

Matthias Pohl commented on FLINK-29671:
---------------------------------------

Also permission issues. Build #45588 and #45587 ran at almost the same time
* 
https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=45587&view=logs&j=bea52777-eaf8-5663-8482-18fbc3630e81&t=b2642e3a-5b86-574d-4c8a-f7e2842bfb14&l=4818
* 
https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=45587&view=logs&j=e9d3d34f-3d15-59f4-0e3e-35067d100dfe&t=f8a6d3eb-38cf-5cca-9a99-d0badeb5fe62&l=5852

> Kubernetes e2e test fails during test initialization
> ----------------------------------------------------
>
>                 Key: FLINK-29671
>                 URL: https://issues.apache.org/jira/browse/FLINK-29671
>             Project: Flink
>          Issue Type: Bug
>          Components: Deployment / Kubernetes, Test Infrastructure
>    Affects Versions: 1.16.0, 1.17.0, 1.15.3
>            Reporter: Matthias Pohl
>            Priority: Critical
>              Labels: starter, test-stability
>         Attachments: kubernetes_test_failure.log
>
>
> There are two build failures ([branch based on 
> release-1.16|https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=42038&view=logs&j=bea52777-eaf8-5663-8482-18fbc3630e81&t=b2642e3a-5b86-574d-4c8a-f7e2842bfb14&l=5377]
>  and [a release-1.15 
> build|https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=42073&view=logs&j=bea52777-eaf8-5663-8482-18fbc3630e81&t=b2642e3a-5b86-574d-4c8a-f7e2842bfb14&l=4684])
>  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:
> {code}
> 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..
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to