-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker container not building due to missing S3 artifact #4544
Comments
Can this still be reproducible ? I could not. @stefanAMB |
Hi @oguzkaganozt, I am afraid it's till the same for me. The issue is still with an artifact download. Here are the logs.
As you can see the error is still a failing connection to and S3 store. I digged it too. Here's the outcome wasabisys.com ✅
ap-northeast-2.wasabisys.com ✅
s3.ap-northeast-2.wasabisys.com ❌
Consequently, the issue persists w/ curl or wget
The network I am using is located in Thuringia/Germany. I was able to connect to the host from a different network (in Berlin/Germany). I'll have to investigate if there's sth in the local network that prevents it once the NW manager is back in (next monday) and report. |
Ok, I investigated a bit more. See the following tracereoutes traceroute to s3.ap-northeast-2.wasabisys.com (23.200.237.238), 30 hops max, 60 byte packets
1 fritz.box (192.168.178.1) 0.498 ms 0.548 ms
2 ber1001fihr001.versatel.de (62.214.63.105) 3.157 ms 2.819 ms
3 vlan213.100M.flensburg1.distribution.komtel.net (62.214.0.77) 2.429 ms 2.328 ms
4 versatel-ic-326760.ip.twelve99-cust.net (213.155.129.191) 2.381 ms 2.492 ms
5 * 212.162.40.37 (212.162.40.37) 2.992 ms
6 be3341.rcr71.ber01.atlas.cogentco.com (154.54.60.1) 14.528 ms 14.385 ms
7 hbg-bb3-link.ip.twelve99.net (62.115.137.40) 9.518 ms be3141.ccr41.ham01.atlas.cogentco.com (130.117.49.137) 14.635 ms
8 4.53.31.70 (4.53.31.70) 155.526 ms !N * versus
Fiddling a bit I found that the --- a/ansible/roles/artifacts/tasks/main.yaml
+++ b/ansible/roles/artifacts/tasks/main.yaml
@@ -8,7 +8,7 @@
- name: Download yabloc_pose_initializer/resources.tar.gz
become: true
ansible.builtin.get_url:
- url: https://s3.ap-northeast-2.wasabisys.com/pinto-model-zoo/136_road-segmentation-adas-0001/resources.tar.gz
+ url: https://ap-northeast-2.wasabisys.com/pinto-model-zoo/136_road-segmentation-adas-0001/resources.tar.gz
dest: "{{ data_dir }}/yabloc_pose_initializer/resources.tar.gz"
mode: "644"
checksum: sha256:1f660e15f95074bade32b1f80dbf618e9cee1f0b9f76d3f4671cb9be7f56eb3a I just checked an all images are built as expected. Not sure if this is then worthy a PR as it might be related to some network issues that aren't really the concern here. |
Thanks for the heads up @stefanAMB, but the network issue looks like resolved for now. |
Checklist
Description
I am trying to build autoware docker images but it consistently fails due to not being able to download an S3 artifact. Logs say:
Trying to manually get the asset (wget or Chrome) also fails saying address unreachable. Further logs are below.
Expected behavior
I expect to be able to run
./docker/build.sh
without any issues.Actual behavior
The actual behaviour is given above. Task [autoware.dev_evn.artifacts] fails with:
Steps to reproduce
Assuming you cloned the repo do:
git checkout main
git fetch
cd docker
./build.sh
Versions
No response
Possible causes
I assume the host s3.ap-northeast-2.wasabisys.com is simply offline.
Additional context
No response
The text was updated successfully, but these errors were encountered: