Getting 403 error randomly when installing temurin packages #923
Comments
|
@angaaruriakhil Can you try updating you ca-certificates package and try again? |
|
Got the same issue here - even after It worked after an |
|
@gdams over to you - I can only imagine a CDN issue? |
|
We are intermittently seeing this issue as well, specifically via Example $ sudo yum install -y temurin-11-jdk
Loaded plugins: extras_suggestions, langpacks, priorities, update-motd
# [ dependency resolution omitted for brevity's sake ]
Total size: 160 M
Total download size: 159 M
Installed size: 314 M
Downloading packages:
No Presto metadata available for Adoptium
temurin-11-jdk-11.0.20.1.0.1-1 FAILED
https://packages.adoptium.net/artifactory/rpm/amazonlinux/2/x86_64/Packages/temurin-11-jdk-11.0.20.1.0.1-1.x86_64.rpm: [Errno 14] HTTPS Error 403 - Forbidden ] 0.0 B/s | 0 B --:--:-- ETA
Trying other mirror.
Error downloading packages:
temurin-11-jdk-11.0.20.1.0.1-1.x86_64: [Errno 256] No more mirrors to try.I encountered this failure several times over starting at 14:55 UTC today, but in my case only for the temurin-11-jdk package; I was able to successfully download and install temurin-11-jre as well as temurin-17-jdk, but temurin-11-jdk continued to fail. As had been suggested on this issue and issue #554, I tried both updating the ca-certificates package and running $ curl -vLO https://packages.adoptium.net/artifactory/rpm/amazonlinux/2/x86_64/Packages/temurin-11-jdk-11.0.20.1.0.1-1.x86_64.rpm
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Trying 146.75.39.42:443...
* Connected to packages.adoptium.net (146.75.39.42) port 443
* ALPN: curl offers h2,http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
} [5 bytes data]
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
* CAfile: /etc/pki/tls/certs/ca-bundle.crt
* CApath: none
{ [5 bytes data]
* TLSv1.2 (IN), TLS handshake, Server hello (2):
{ [100 bytes data]
* TLSv1.2 (IN), TLS handshake, Certificate (11):
{ [3978 bytes data]
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
{ [333 bytes data]
* TLSv1.2 (IN), TLS handshake, Server finished (14):
{ [4 bytes data]
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
} [70 bytes data]
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
} [1 bytes data]
* TLSv1.2 (OUT), TLS handshake, Finished (20):
} [16 bytes data]
* TLSv1.2 (IN), TLS change cipher, Change cipher spec (1):
{ [1 bytes data]
* TLSv1.2 (IN), TLS handshake, Finished (20):
{ [16 bytes data]
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN: server accepted h2
* Server certificate:
* subject: CN=packages.adoptium.net
* start date: Oct 2 11:22:18 2023 GMT
* expire date: Dec 31 11:22:17 2023 GMT
* subjectAltName: host "packages.adoptium.net" matched cert's "packages.adoptium.net"
* issuer: C=US; O=Let's Encrypt; CN=R3
* SSL certificate verify ok.
} [5 bytes data]
* using HTTP/2
* [HTTP/2] [1] OPENED stream for https://packages.adoptium.net/artifactory/rpm/amazonlinux/2/x86_64/Packages/temurin-11-jdk-11.0.20.1.0.1-1.x86_64.rpm
* [HTTP/2] [1] [:method: GET]
* [HTTP/2] [1] [:scheme: https]
* [HTTP/2] [1] [:authority: packages.adoptium.net]
* [HTTP/2] [1] [:path: /artifactory/rpm/amazonlinux/2/x86_64/Packages/temurin-11-jdk-11.0.20.1.0.1-1.x86_64.rpm]
* [HTTP/2] [1] [user-agent: curl/8.3.0]
* [HTTP/2] [1] [accept: */*]
} [5 bytes data]
> GET /artifactory/rpm/amazonlinux/2/x86_64/Packages/temurin-11-jdk-11.0.20.1.0.1-1.x86_64.rpm HTTP/2
> Host: packages.adoptium.net
> User-Agent: curl/8.3.0
> Accept: */*
>
{ [5 bytes data]
< HTTP/2 200
< x-amz-id-2: H5ntxCxOdyFhTEZa+JrnjbA2V9VdbpXoFdCeekzjgSGgWSBi/YUbTChNj90JUOuqUxyWHrANR+A=
< x-amz-request-id: QJZ3FQGCMJW8Z84N
< x-amz-replication-status: FAILED
< last-modified: Thu, 31 Aug 2023 12:51:43 GMT
< etag: "71b38a94dbeff6f692cf13a3b7038f35"
< x-amz-server-side-encryption: AES256
< x-amz-version-id: umzWdTNJmMDdvnR0unSw_fRTy4j1NfZd
< content-disposition: attachment;filename="temurin-11-jdk-11.0.20.1.0.1-1.x86_64.rpm"
< content-type: application/x-rpm
< server: AmazonS3
< cache-control: public, max-age=15780096.000
< fastly-restarts: 1
< accept-ranges: bytes
< date: Tue, 24 Oct 2023 15:13:19 GMT
< via: 1.1 varnish
< age: 3022
< x-served-by: cache-iad-kcgs7200148-IAD
< x-cache: HIT
< x-cache-hits: 1
< x-timer: S1698160399.397782,VS0,VE2
< strict-transport-security: max-age=31557600
< content-length: 166352397
<
{ [5 bytes data]
* HTTP/2 stream 1 was not closed cleanly: PROTOCOL_ERROR (err 1)
60 158M 60 96.0M 0 0 166M 0 --:--:-- --:--:-- --:--:-- 166M
* Connection #0 to host packages.adoptium.net left intact
curl: (92) HTTP/2 stream 1 was not closed cleanly: PROTOCOL_ERROR (err 1)This failed command actually did download 96M – other attempts downloaded different amounts – but it always failed. The error message implying that the stream wasn't closed cleanly leads me to wonder if the cached asset is corrupt, or perhaps isn't fully-distributed/cached by the CDN? I'm not sure if/how $ curl -vLO https://packages.adoptium.net/artifactory/rpm/amazonlinux/2/x86_64/Packages/temurin-17-jdk-17.0.8.1.0.1-1.x86_64.rpm
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Trying 146.75.35.42:443...
* Connected to packages.adoptium.net (146.75.35.42) port 443
* ALPN: curl offers h2,http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
} [5 bytes data]
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
* CAfile: /etc/pki/tls/certs/ca-bundle.crt
* CApath: none
{ [5 bytes data]
* TLSv1.2 (IN), TLS handshake, Server hello (2):
{ [100 bytes data]
* TLSv1.2 (IN), TLS handshake, Certificate (11):
{ [3978 bytes data]
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
{ [333 bytes data]
* TLSv1.2 (IN), TLS handshake, Server finished (14):
{ [4 bytes data]
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
} [70 bytes data]
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
} [1 bytes data]
* TLSv1.2 (OUT), TLS handshake, Finished (20):
} [16 bytes data]
* TLSv1.2 (IN), TLS change cipher, Change cipher spec (1):
{ [1 bytes data]
* TLSv1.2 (IN), TLS handshake, Finished (20):
{ [16 bytes data]
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN: server accepted h2
* Server certificate:
* subject: CN=packages.adoptium.net
* start date: Oct 2 11:22:18 2023 GMT
* expire date: Dec 31 11:22:17 2023 GMT
* subjectAltName: host "packages.adoptium.net" matched cert's "packages.adoptium.net"
* issuer: C=US; O=Let's Encrypt; CN=R3
* SSL certificate verify ok.
} [5 bytes data]
* using HTTP/2
* [HTTP/2] [1] OPENED stream for https://packages.adoptium.net/artifactory/rpm/amazonlinux/2/x86_64/Packages/temurin-17-jdk-17.0.8.1.0.1-1.x86_64.rpm
* [HTTP/2] [1] [:method: GET]
* [HTTP/2] [1] [:scheme: https]
* [HTTP/2] [1] [:authority: packages.adoptium.net]
* [HTTP/2] [1] [:path: /artifactory/rpm/amazonlinux/2/x86_64/Packages/temurin-17-jdk-17.0.8.1.0.1-1.x86_64.rpm]
* [HTTP/2] [1] [user-agent: curl/8.3.0]
* [HTTP/2] [1] [accept: */*]
} [5 bytes data]
> GET /artifactory/rpm/amazonlinux/2/x86_64/Packages/temurin-17-jdk-17.0.8.1.0.1-1.x86_64.rpm HTTP/2
> Host: packages.adoptium.net
> User-Agent: curl/8.3.0
> Accept: */*
>
{ [5 bytes data]
< HTTP/2 200
< x-amz-id-2: xUHOk3FxG3CALkYV/8zV6BjfkJl7o9PVSMO6jAXu1BBEKzEi8qRBbhPN+6SrCDSncmHJE9JYhqc=
< x-amz-request-id: 9FDX85EN3B8YFEC4
< x-amz-replication-status: FAILED
< last-modified: Thu, 31 Aug 2023 14:32:03 GMT
< etag: "a8ed74787d123dc1a9664b59a4c14ca2"
< x-amz-server-side-encryption: AES256
< x-amz-version-id: Z1zAzlEUB_ubAmeOULSp6EX2L.7XXn9A
< content-disposition: attachment;filename="temurin-17-jdk-17.0.8.1.0.1-1.x86_64.rpm"
< content-type: application/x-rpm
< server: AmazonS3
< cache-control: public, max-age=15780096.000
< fastly-restarts: 1
< accept-ranges: bytes
< date: Tue, 24 Oct 2023 16:12:30 GMT
< via: 1.1 varnish
< age: 0
< x-served-by: cache-iad-kjyo7100121-IAD
< x-cache: MISS
< x-cache-hits: 0
< x-timer: S1698163950.013750,VS0,VE913
< strict-transport-security: max-age=31557600
< content-length: 162689473
<
{ [5 bytes data]
100 155M 100 155M 0 0 9496k 0 0:00:16 0:00:16 --:--:-- 10.2M
* Connection #0 to host packages.adoptium.net left intactDiffing the two downloads, I noted this first download of temurin-17-jdk-17.0.8.1.0.1-1.x86_64.rpm showed a cache MISS; subsequent requests for the same URL were also successful and showed a cache HIT (as did all my requests for temurin-11-jdk-11.0.20.1.0.1-1.x86_64.rpm), but otherwise they appear functionally similar (no appreciable difference that might point to a reason for the "stream 1 was not closed cleanly" errors that I can see, anyways). I lost track of the exact time while I was debugging all this, but at some point between 20-30 minutes later, a stray |
|
Thanks for the responses folks, I have not seen this issue this week on our builds, we've had 4 successful builds with temurin 8, 11, 17, and 21 installing on each build without issue. Haven't changed anything in our code since my last post. I'm in agreement with the above that it's possibly artifactory/CDN related... |
|
I don't agree that this issue should be closed – I experienced this issue just yesterday, as documented above – and even if we accept the premise that this is a transient issue, it is still a persistent issue that deserves further investigation. |
|
Got the issue again. This time a variable ${VERSION} in the download URL target seems not to be resolved: olger@phobos:~$ sudo apt upgrade
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
Paketaktualisierung (Upgrade) wird berechnet… Fertig
Die folgenden Pakete werden aktualisiert (Upgrade):
temurin-17-jdk temurin-21-jdk
2 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
Es müssen 343 MB an Archiven heruntergeladen werden.
Nach dieser Operation werden 197 kB Plattenplatz zusätzlich benutzt.
Möchten Sie fortfahren? [J/n]
Fehl:1 https://packages.adoptium.net/artifactory/deb bookworm/main amd64 temurin-17-jdk amd64 17.0.9.0+9
400 Bad Request [IP: 146.75.123.42 443]
Fehl:2 https://packages.adoptium.net/artifactory/deb bookworm/main amd64 temurin-21-jdk amd64 21.0.1.0.0+12
400 Bad Request [IP: 146.75.123.42 443]
E: Fehlschlag beim Holen von https://packages.adoptium.net/artifactory/deb/pool/main/t/temurin-${VERSION}/temurin-17-jdk_17.0.9.0%2b9_amd64.deb 400 Bad Request [IP: 146.75.123.42 443]
E: Fehlschlag beim Holen von https://packages.adoptium.net/artifactory/deb/pool/main/t/temurin-${VERSION}/temurin-21-jdk_21.0.1.0.0%2b12_amd64.deb 400 Bad Request [IP: 146.75.123.42 443]
E: Einige Archive konnten nicht heruntergeladen werden; vielleicht »apt-get update« ausführen oder mit »--fix-missing« probieren?
Is says "failed to get" |
|
I'm having the same issue on Linux Mint 20 (Ubuntu 20.04) I updated certificates and tried --fix-missing. No joy. |
|
Same issue here on Ubuntu 22.04 after updating ca-certs and trying --fix-missing |
|
Hi folks, we're aware of the issue and are investigating with our CDN and package repo providers. |
|
To anyone making an update to a URL that contains The second bug is around the different behaviour that artifactory serves users if they are in a browser or on a command line. If you make a request in the browser it creates a 301 redirect to a /ui route so that you can explore the repo in artifactory whereas in the command line, it should always serve the binary. I’ve managed to create some code that synthetically handles these 301’s for browser users which should mean that Fastly stops caching the wrong response. |
|
Works now. Thank you. |
|
this is not solved... wget https://packages.adoptium.net/artifactory/rpm/amazonlinux/2/x86_64/Packages/temurin-17-jdk-17.0.9.0.0.9-1.x86_64.rpm 61% [====================================================================> ] 100,663,296 312MB/s in 0.3s 2023-10-31 12:38:50 (312 MB/s) - Connection closed at byte 100663296. Retrying. --2023-10-31 12:38:51-- (try: 2) https://packages.adoptium.net/artifactory/rpm/amazonlinux/2/x86_64/Packages/temurin-17-jdk-17.0.9.0.0.9-1.x86_64.rpm wget https://packages.adoptium.net/artifactory/rpm/amazonlinux/2/x86_64/Packages/temurin-17-jdk-17.0.9.0.0.9-1.x86_64.rpm 61% [====================================================================> ] 100,663,296 294MB/s in 0.3s 2023-10-31 12:41:40 (294 MB/s) - Connection closed at byte 100663296. Retrying. --2023-10-31 12:41:41-- (try: 2) https://packages.adoptium.net/artifactory/rpm/amazonlinux/2/x86_64/Packages/temurin-17-jdk-17.0.9.0.0.9-1.x86_64.rpm |
|
Hi, we have been experiencing this issue again today. |
|
I'm talking with Fastly again today, I think that Fastly is caching incomplete requests and then continuing to serve them rather than routing users directly to Artificatory. I'll provide an update here once I have one. |
|
Still having this issue. Failed to fetch Error reading from server. Remote end closed connection |
@xsnrg can you share the full URL that you are trying to request? |
|
sure thing. It seems to be working again this morning. |
|
@gdams: Seems like this issue is happening somewhat frequently for me as well: |
|
This is inconsistent and still requires attention. Most of the time In the very rare case the binary is able to download it often fails with When persistent, there will a rare occasion when it works (which some people posting above when it "appears to be working again".... are likely getting the lucky one off. |
|
I am seeing this as well today when installing Adoptium JDK 11 via Flintrock, which installs JDK on instances launched on EC2: Is there some more information I can share to help identify the root cause here? |
|
I was getting I got the chance to get some information in case it is useful to find the root cause by using Ubuntu APT debugging options ( Also, I observed that the 403 is not thrown at the very beginning but after some content is already downloaded (~15 %). I guess that APT opens multiple connections to download packages and a one of those workers got the 403 failing the rest of the download: Here are the outputs of APT with debug options when it failed and when it worked: Failed with 403 downloading latest versionDownloaded latest version some minutes laterI suggest looking to Just for reference, these are other reported issues that I come across while researching the problem.... it seems that the issue is not new: |
|
We too are facing this issue everyday, and it is not clear why.... Only during some moments we can actually install the package... is there any alternative for https://packages.adoptium.net/artifactory/deb that it is more reliable? or any known mitigation for this? Thank you |
|
Also affected, when trying to build runner-images, blocking new releases of the same image. Thanks for looking into it. |
|
I was reproducing this issue on last Thursday but not anymore today. Seems it has been fixed. |
|
Still issue... |
|
one workaround is to simply download the .deb from the website, you may need to change the url to get it to work, but just use |
|
I was able to resolve this issue by using the Mac .dmg version instead of the Linux version
…On Monday, January 29th, 2024 at 13:14, Andrew ***@***.***> wrote:
one workaround is to simply download the .deb from the website, you may need to change the url to get it to work, but just use dpkg - i
—
Reply to this email directly, [view it on GitHub](#923 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AFB6HBOXLEF7GL6RCHTOZH3YRAGMNAVCNFSM6AAAAAA6JQKDZGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJVGU4DENZRGM).
You are receiving this because you commented.Message ID: ***@***.***>
|
|
received 403 and 503 errors as well as Hash Sum mismatch yesterday: E: Failed to fetch https://packages.adoptium.net/artifactory/deb/pool/main/t/temurin-17/temurin-17-jdk_17.0.10.0.0%2b7_amd64.deb 503 Response object too large [IP: 151.101.3.42 443] E: Failed to fetch https://packages.adoptium.net/artifactory/deb/pool/main/t/temurin-17/temurin-17-jdk_17.0.10.0.0%2b7_amd64.deb 403 Forbidden [IP: 151.101.67.42 443] E: Failed to fetch https://packages.adoptium.net/artifactory/deb/pool/main/t/temurin-17/temurin-17-jdk_17.0.10.0.0%2b7_amd64.deb 403 Forbidden [IP: 151.101.131.42 443] E: Failed to fetch https://packages.adoptium.net/artifactory/deb/pool/main/t/temurin-17/temurin-17-jdk_17.0.10.0.0%2b7_amd64.deb 503 Response object too large [IP: 151.101.195.42 443] E: Failed to fetch https://packages.adoptium.net/artifactory/deb/pool/main/t/temurin-17/temurin-17-jdk_17.0.10.0.0%2b7_amd64.deb Hash Sum mismatch |
|
Still facing this issue ==> azure-arm.build_image: <- https:102%20Status%0aMessage:%20Waiting%20for%20headers%0aURI:%20https://packages.adoptium.net/artifactory/deb/pool/main/t/temurin-11/temurin-11-jdk_11.0.22.0.0%252b7_amd64.deb |
|
This error is continuing to occur for at least Temurin 11 and 21 packages. 10:22:54 Reading package lists... 11:22:06 Reading package lists... |
|
We are facing this issue (a bunch of 403 errors trying to bootstrap, same as @ericlayton shared). @gdams any update in this one ? Maybe @mbarbero can help ? |
|
Forbidden error happening with an Ubuntu 20.04 while running Lendo listas de pacotes... Pronto
Construindo árvore de dependências
Lendo informação de estado... Pronto
Calculando atualização... Pronto
Obtenha mais atualizações de segurança através do Ubuntu Pro com 'esm-apps' habilitado:
libavformat58 libmagick++-6.q16-8 libavfilter7 libimage-magick-perl
libmagickcore-6.q16-6-extra libimage-magick-q16-perl imagemagick
libswresample3 libgegl-0.4-0 libzmq5 libmagickwand-6.q16-6 libgegl-common
libcgraph6 libpostproc55 liblab-gamut1 imagemagick-6.q16 libavcodec58
libcdt5 libavutil56 libpathplan4 libswscale5 libgvpr2 libopenexr24
libsdl2-2.0-0 libmysofa1 libmagickcore-6.q16-6 libgvc6 graphviz
imagemagick-6-common
Saiba mais sobre o Ubuntu Pro em https://ubuntu.com/pro
Os pacotes a seguir serão atualizados:
temurin-21-jdk
1 pacotes atualizados, 0 pacotes novos instalados, 0 a serem removidos e 0 não atualizados.
É preciso baixar 178 MB de arquivos.
Depois desta operação, 738 kB adicionais de espaço em disco serão usados.
Você quer continuar? [S/n]
Err:1 https://packages.adoptium.net/artifactory/deb focal/main amd64 temurin-21-jdk amd64 21.0.2.0.0+13-2
403 Forbidden [IP: 151.101.3.42 443]
E: Falhou ao buscar https://packages.adoptium.net/artifactory/deb/pool/main/t/temurin-21/temurin-21-jdk_21.0.2.0.0+13-2_amd64.deb 403 Forbidden [IP: 151.101.3.42 443]
E: Impossível buscar alguns arquivos, talvez executar apt-get update ou tentar com --fix-missing? |
|
We are still facing this issue (randomly but pretty often). It's basically the same as @mhever. I'm trying a bunch of It would be great to have an update from Adoptium committers and/or Eclipse infra. |
I'm one of the Adoptium PMC members. We are aware of the issue and keep monitoring the situation. For example, we discussed this issue again on the PMC meeting of March 20'th, 2024. Unfortunately, we are unaware of a proper reproducer and given the volume of hits we get to the repository the failure cases are fairly infrequent (relatively speaking, considering the scale). In the absence of a reproducer, there is unfortunately only a limited amount that we can do on our end. We keep monitoring the situation with an eye on the failure rate, however. Having said that, if somebody ends up figuring out what exactly is needed to reliably reproduce the issue we can work on a more permanent solution. As of yet, there is little we can do. Thanks for your understanding! |
|
@jerboaa Thanks for your feedback ! I agree, I'm also struggling to reproduce the behavior on my machine, it seems way more frequent on our cloud infra. Thanks again ! |
|
Got the error today: wget -qO - https://packages.adoptium.net/artifactory/api/gpg/key/public | gpg --dearmor > /usr/share/keyrings/adoptium.gpg
echo "deb [signed-by=/usr/share/keyrings/adoptium.gpg] https://packages.adoptium.net/artifactory/deb/ $(lsb_release -cs) main" > /etc/apt/sources.list.d/adoptium.list
apt-get -q update
apt-get -q install temurin-17-jdk=\*It worked 2 hours ago, now I can't get through after multiple tries EDIT: It started working after an hour |
|
I'm also experiencing similar issue today. (Experienced similar issue yesterday, As commented above, sometimes it worked yesterday.) However, again, happending today. EDIT: Same as above. It started working now. |
|
Getting the same issue when trying to use packer image for Ubuntu 20.04 |
|
The same situation on Centos7, wget, curl, dnf, and yum. |
|
Hit this today for temurin-8: |
|
If Fastly isn't able to solve this issue, it may be worth asking the good folks at Cloudflare if they'd be able to help out with CDN? |
|
Facing the issue today too in a CD script |
|
This issue is blocking some playbooks from running when setting up new hosts. |
|
And today as well |
|
Same happening for me occasionally on AWS EC2 with Debian 12. apt and wget resulting in a 403. from my local machine it's working fine. The only way for me to fix it was to change the Elastic IP / NAT Gateway as the AWS IP really seemed to be blacklisted. |
|
I've been encountering this issue, when I copy the link to my browser and try the same request, I can see that the request has already expired. Note: Expires vs ServerTime |
|
We are marking this issue as stale because it has not been updated for a while. This is just a way to keep the support issues queue manageable. |
and others
We are conducting ubuntu 20.04 image builds using code in the runner-images repository.
When installing temurin JDK packages, we now get 403 errors randomly on differing packages.
We conducted a build yesterday which failed on installing temurin 21 with the following error:
azure-arm: E: Failed to fetch https://packages.adoptium.net/artifactory/deb/pool/main/t/temurin-21/temurin-21-jdk_21.0.0.0.0+35_amd64.deb 403 Forbidden [IP: 146.75.107.42 443]We conducted a build today which failed on temurin 11 with the following error:
azure-arm.build_vhd: E: Failed to fetch https://packages.adoptium.net/artifactory/deb/pool/main/t/temurin-11/temurin-11-jdk_11.0.20.1.0%2b1_amd64.deb Error reading from server. Remote end closed connection [IP: 146.75.107.42 443]We have also had some successful builds where all the packages install.
To Reproduce
Run code in java-tools.sh to install temurin packages.
Expected behavior
Every package is able to be installed reliably
The text was updated successfully, but these errors were encountered: