Verify fakeroot is available on all arm_linux machines

[smlambert]

Not unlike the 5 closed infrastructure issues related to fakeroot missing on other platforms, need to verify that all arm_linux machines are also capable of running the jdk_tools target from the extended.openjdk top-level target (see adoptium/aqa-tests#4257 (comment) for details).

To make it easy for the infrastructure team to repeat and diagnose, please
answer the following questions:

• test suite/name (e.g, BUILD_LIST, TARGET, CUSTOM_TARGET)? BUILD_LIST=openjdk TARGET=jdk_tools
• a link into recent Test_ job on https://ci.adoptium.net which showed the failure
  https://ci.adoptium.net/job/Test_openjdk19_hs_extended.openjdk_arm_linux_testList_0/34/
• Hyperlink to re-run in Grinder: rerun link
• Is there an existing issue elsewhere covering this? No, but 5 similar closed issues linked above
• Which machine(s) does it work on? test-docker-ubuntu2004-armv7l-2
• Which machine(s) does it fail on? test-docker-ubuntu2204-armv8-2

Any other details:

[15:18:20.405] Running fakeroot
[15:18:20.412] jdk.jpackage.internal.ConfigException: Can not find fakeroot. Reason: Cannot run program "fakeroot": error=2, No such file or directory
	at jdk.jpackage/jdk.jpackage.internal.ToolValidator.validate(ToolValidator.java:122)
	at jdk.jpackage/jdk.jpackage.internal.LinuxPackageBundler.validate(LinuxPackageBundler.java:76)
	at jdk.jpackage/jdk.jpackage.internal.Arguments.generateBundle(Arguments.java:699)
	at jdk.jpackage/jdk.jpackage.internal.Arguments.processArguments(Arguments.java:565)
	at jdk.jpackage/jdk.jpackage.main.Main.execute(Main.java:91)
	at jdk.jpackage/jdk.jpackage.main.Main.main(Main.java:52)
Caused by: java.io.IOException: Cannot run program "fakeroot": error=2, No such file or directory
	at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1143)
	at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1073)
	at jdk.jpackage/jdk.jpackage.internal.Executor.execute(Executor.java:116)
	at jdk.jpackage/jdk.jpackage.internal.ToolValidator.validate(ToolValidator.java:104)
	... 5 more
Caused by: java.io.IOException: error=2, No such file or directory
	at java.base/java.lang.ProcessImpl.forkAndExec(Native Method)
	at java.base/java.lang.ProcessImpl.<init>(ProcessImpl.java:319)
	at java.base/java.lang.ProcessImpl.start(ProcessImpl.java:249)
	at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1110)
	... 8 more

Rerun jdk_tools at: https://ci.adoptium.net/job/Grinder/6728 for a fresh run on test-docker-ubuntu2204-armv8-2 to check if it is still an issue. Rerun just the failing testcases at this link.

[smlambert]

https://ci.adoptium.net/job/Test_openjdk20_hs_extended.openjdk_aarch64_linux/22/testReport/tools_jpackage_linux_LinuxBundleNameTest/java/LinuxBundleNameTest_2/

Also appears to be missing from some aarch64 linux machines.

[smlambert]

This will affect the JDK 20 release if not addressed. We may want to disable machines in order to avoid sending test jobs off to certain failure.

[sxa]

Hmmm - test-docker-ubuntu2204-armv8-2 appears to incorrectly have the hw.arch.aarch32 tag on it (as per the hostname, it's armv8 which =aarch64) so the job shouldn't even be trying to run there. I'll remove that label (although that doesn't directly explain why fakeroot wasn't able to be executed as it seems to be present...) It's (wrongly) running https://ci.adoptium.net/job/Test_openjdk19_hs_extended.openjdk_arm_linux_testList_0/38/ just now

Note to self: Using this to check the docker containers on each host: docker ps | grep -v NAMES | awk '{print$NF}' | while read X; do docker exec $X sh -c "which fakeroot >/dev/null || echo Nothing on $X"; done

Running through the dockerhost systems:

• test-equinix-ubuntu2004-armv8l-02 147.75.35.203 (3 remediated, U2010_2231 shut down as it's out of support)
• dockerhost-equinix-ubuntu2204-armv8-1 (No issues)
• dockerhost-equinix-ubuntu2004-x64-1 (No issues)
• dockerhost-equinix-ubuntu2204-x64-1 (No issues)
• dockerhost-osuosl-ubuntu2204-ppc64le-1 (U2010_2225 obsolete OS - disabled, U1804_2223 fixed, F33_2227 fixed)
• dockerhost-marist-ubuntu2204-s390x-1 - All OK (Only SLES)
• docker-skytap-ubuntu2004-ppc64le-1 - All OK
• dockerhost-skytap-ubuntu2004-ppc64le-2 - All OK

[sxa]

Disappearing down a rabbit hole - test-docker-ubuntu2204-armv8-2 is actually an ARM32 container which is why the arm32 jobs are running ok on it - I've just renamed it to https://ci.adoptium.net/computer/test-docker-ubuntu2204-armv7l-1/

[sxa]

Also installed on test-marist-rhel8-s390x-2 and test-marist-sles15-s390x-2 although it does not seem to be installable on test-marist-rhel7-s390x-2 so I'm going to mark that one offline for now...

[sxa]

Noting here that this is complete as far as jenkins job reliability is concerned but there are some machines that have been taken offline as notes above as they were not a "quick fix" so I'm leaving this open for now:

• Ubuntu 21.10 systems (DockerStatic hosts that need to be replaced/removed
• test-marist-rhel7-s390x-2

[Haroon-Khel]

The ubuntu 2110 system is decommissioned and removed from jenkins

[sxa]

Sine the only remaining machine which isn't set up with this is the RHEL7 one and we can't easily install it from the repositories on there at the moment, I'm going to create another issue for that one.