Look at setting up Ubuntu 24.04

[sxa]

Ubuntu 24.04 will be out later this month. We should look at our existing inventory and make some of these available. This will involve:

• Identifying older systems that can be replaced with Ubuntu 24.04 without restricting testing.
• Having at least one static docker image on each architecture
• Ideally having one real machine for each architecture on this
• Verifying that it is suitable as a base for our dockerhost systems (Maybe replace one of the Azure dockerhost systems that can't be used for VMs with an AMD one running Ubuntu 24.04?)

[Haroon-Khel]

Ubuntu 2404 static docker container online in jenkins https://ci.adoptium.net/computer/test-docker-ubuntu2404-x64-1/

Will run the aqa test pipeline on it shortly

EDIT: https://ci.adoptium.net/job/AQA_Test_Pipeline/237/console

[Haroon-Khel]

Identifying older systems that can be replaced with Ubuntu 24.04 without restricting testing.

In regards to replaceable static docker containers, at the moment we have 3 ubuntu 2004 x64 nodes, 9 arm64 ubuntu 2004 nodes, 1 ubunutu 1804 node, 6 arm32 ubuntu 2004 nodes and 3 ubuntu 2204 ppc64le nodes. I can remove one from each and replace it with a ubuntu 2404 node of that architecture, and make a brand new ubuntu 2404 s390x node on dockerhost-marist-ubuntu2204-s390x-1

[sxa]

Identifying older systems that can be replaced with Ubuntu 24.04 without restricting testing.

In regards to replaceable static docker containers, at the moment we have 3 ubuntu 2004 x64 nodes, 9 arm64 ubuntu 2004 nodes, 1 ubunutu 1804 node, 6 arm32 ubuntu 2004 nodes and 3 ubuntu 2204 ppc64le nodes. I can remove one from each and replace it with a ubuntu 2404 node of that architecture, and make a brand new ubuntu 2404 s390x node on dockerhost-marist-ubuntu2204-s390x-1

SGTM - we can start with that and then probably look at migrating more of the 2004 ones up given how many we have. I hadn't spotted that we don't even have 22.04 on arm32.

[Haroon-Khel]

https://ci.adoptium.net/computer/test-docker-ubuntu2404-armv8-1/ https://ci.adoptium.net/job/AQA_Test_Pipeline/239/console

https://ci.adoptium.net/computer/test-docker-ubuntu2404-s390x-1/ https://ci.adoptium.net/job/AQA_Test_Pipeline/240/console

Getting unusual errors while building the ppc64le and arm32 images

 > [ 7/25] RUN mkdir -p /usr/lib/jvm/jdk17 && tar -xpzf /tmp/jdk17.tar.gz -C /usr/lib/jvm/jdk17 --strip-components=1:                                                                                               
0.295 tar: conf/security/policy/unlimited: Cannot change mode to rwxr-xr-x: Operation not permitted                                                                                                                 
0.295 tar: conf/security/policy/limited: Cannot change mode to rwxr-xr-x: Operation not permitted                                                                                                                   
0.295 tar: conf/security/policy: Cannot change mode to rwxr-xr-x: Operation not permitted                                                                                                                           
0.295 tar: conf/security: Cannot change mode to rwxr-xr-x: Operation not permitted                                                                                                                                  
0.295 tar: conf/sdp: Cannot change mode to rwxr-xr-x: Operation not permitted
0.296 tar: conf/management: Cannot change mode to rwxr-xr-x: Operation not permitted
0.296 tar: conf: Cannot change mode to rwxr-xr-x: Operation not permitted
0.305 tar: legal/java.base: Cannot change mode to rwxr-xr-x: Operation not permitted
1.052 tar: jmods: Cannot change mode to rwxr-xr-x: Operation not permitted

[Haroon-Khel]

Got the remaining nodes up and running by building them manually

https://ci.adoptium.net/computer/test-docker-ubuntu2404-ppc64le-1/
https://ci.adoptium.net/job/AQA_Test_Pipeline/242/console

https://ci.adoptium.net/computer/test-docker-ubuntu2404-armv7l-1/
https://ci.adoptium.net/job/AQA_Test_Pipeline/241/console

[sxa]

Unfortunately we don't have an easy way of provisioning a 24.04 on arm32 or ppc64le at the moment to identify whether this is specific to running in a container.

[sxa]

It looks like we're getting some interesting new errors in the sanity.openjdk
Also in the extended run we're getting quite a lot of failures some of which are related to dpkg so are likely related to the new version (I'm quite surprised that the tests are doing things at that OS-specific level, but apparently they do!):

 [09:14:04.910] Running dpkg
 [09:14:06.077] Command [PID: 1034473]:
     dpkg -S /lib/x86_64-linux-gnu/libbrotlidec.so.1
 [09:14:06.077] Output:
     dpkg-query: no path found matching pattern /lib/x86_64-linux-gnu/libbrotlidec.so.1
 [09:14:06.077] Returned: 1
 
 [09:14:06.078] java.io.IOException: Command [dpkg, -S, /lib/x86_64-linux-gnu/libbrotlidec.so.1] exited with 1 code

Based on this I think it's worth getting a "real" ubuntu 24.04 provisioned somewhere and verify that nothing we're seeing is the result of using an earlier kernel version with a newer container.

[Haroon-Khel]

OSUOSL's openstack and azure dont seem to have a ubuntu2404 image (yet)

[sxa]

This is where having the ESXi server was useful :-)

[sxa]

Will run the aqa test pipeline on it shortly
EDIT: https://ci.adoptium.net/job/AQA_Test_Pipeline/237/console

To keep the machines busy over the UK bank holiday weekend I've kicked that off again with all the other versions at https://ci.adoptium.net/job/AQA_Test_Pipeline/243/

[sxa]

Got the remaining nodes up and running by building them manually

https://ci.adoptium.net/job/AQA_Test_Pipeline/242/console (ppc64le)
https://ci.adoptium.net/job/AQA_Test_Pipeline/241/console (arm32)

Noting that those seem to be failing after the tarball extraction had the same problem you had with the docker image creation

[Haroon-Khel]

Ive marked both machines offline so they dont affect the weekend nightlies

[sxa]

I've just ran the Dockerfile for s390x and ppc64le in an emulated docker on an arm64 Ubuntu 24.04 host and they both worked without any permission issues 🤔
So the docker Ubuntu images on those platforms are not fundamentally broken.

[sxa]

I'm doing some re-runs based on the "clean" (green) sanity.openjdk jobs that I was doing as part of adoptium/temurin-build#3685 (comment) (the x64 -cfi-vh row) with JDK22+35:

• Same machine as before (test-docker-ubuntu2004-x64-2 ✅
• The new Ubuntu 24.04 system ✅
• The new Amazon Linux 2023 system (for comparison) ❌ (Failed java/lang/ProcessHandle/InfoTest.java.InfoTest) - rerun ❌

[sxa]

Ubuntu 2404 static docker container online in jenkins https://ci.adoptium.net/computer/test-docker-ubuntu2404-x64-1/

Will run the aqa test pipeline on it shortly

EDIT: https://ci.adoptium.net/job/AQA_Test_Pipeline/237/console

https://ci.adoptium.net/computer/test-docker-ubuntu2404-armv8-1/ https://ci.adoptium.net/job/AQA_Test_Pipeline/239/console
https://ci.adoptium.net/computer/test-docker-ubuntu2404-s390x-1/ https://ci.adoptium.net/job/AQA_Test_Pipeline/240/console

On the basis of the reruns in the previous comment running clean I'm going to re-run these (including extra versions) with ADOPTOPENJDK_BRANCH=v1.0.1-release so that the material matches the product under test (SDK_RESOURCE=releases). These are being run with all versions: 17,8,22,21,11. The original JDK17 runs linked above took 29 hours (x64), 14h (aarch64) and 17 hours (s390x). so the first 2-3 versions will hopefully be mostly complete on Monday morning which will hopefully give enough of a result set that we can determine if there are likely to be any problems.

• x64 - 254 (BlueOcean)
• aarch64 - 257 (BlueOcean)
• s390x - 256 (BlueOcean)