sanity.external failures on xlinux on ibmcloud systems

Please set the title to indicate the test name and machine name where known.

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)? sanity.external (JDK11 specifically analysed)
- a link into recent `Test_` job on https://ci.adoptium.net which showed the failure Most on https://ci.adoptium.net/job/Test_openjdk11_hs_sanity.external_x86-64_linux/589/
- **Hyperlink** to re-run in Grinder: [Link](https://ci.adoptium.net/job/Grinder/parambuild/?SDK_RESOURCE=upstream&TARGET=sanity.external&TEST_FLAG=&UPSTREAM_TEST_JOB_NAME=&DOCKER_REQUIRED=true&ACTIVE_NODE_TIMEOUT=0&EXTRA_DOCKER_ARGS=-v+%24%7BTEST_JDK_HOME%7D%3A%2Fopt%2Fjava%2Fopenjdk&VENDOR_TEST_DIRS=&TKG_OWNER_BRANCH=AdoptOpenJDK%3Amaster&PLATFORM=x86-64_linux&GENERATE_JOBS=false&KEEP_REPORTDIR=false&PERSONAL_BUILD=false&ADOPTOPENJDK_REPO=https%3A%2F%2Fgithub.com%2FAdoptOpenJDK%2Fopenjdk-tests.git&LABEL=&EXTRA_OPTIONS=&CUSTOMIZED_SDK_URL=&BUILD_IDENTIFIER=&ADOPTOPENJDK_BRANCH=master&LIGHT_WEIGHT_CHECKOUT=false&ARTIFACTORY_SERVER=&KEEP_WORKSPACE=false&JDK_VERSION=11&USER_CREDENTIALS_ID=&ITERATIONS=1&VENDOR_TEST_REPOS=&JDK_REPO=https%3A%2F%2Fgithub.com%2Fadoptium%2Fjdk11u&OPENJ9_BRANCH=master&OPENJ9_SHA=&JCK_GIT_REPO=&VENDOR_TEST_BRANCHES=&UPSTREAM_JOB_NAME=build-scripts%2Fjobs%2Fjdk11u%2Fjdk11u-linux-x64-temurin&OPENJ9_REPO=https%3A%2F%2Fgithub.com%2Feclipse%2Fopenj9.git&CUSTOM_TARGET=&VENDOR_TEST_SHAS=&JDK_BRANCH=dev&LABEL_ADDITION=&ARTIFACTORY_REPO=&ARTIFACTORY_ROOT_DIR=&UPSTREAM_TEST_JOB_NUMBER=&DOCKERIMAGE_TAG=nightly&JDK_IMPL=hotspot&SSH_AGENT_CREDENTIAL=&AUTO_DETECT=true&DYNAMIC_COMPILE=true&TKG_SHA=&CUSTOMIZED_SDK_URL_CREDENTIAL_ID=&NUM_MACHINES=&OPENJDK_SHA=&USE_TESTENV_PROPERTIES=false&BUILD_LIST=external&UPSTREAM_JOB_NUMBER=271&TIME_LIMIT=10&JVM_OPTIONS=&PARALLEL=None]
- Is there an existing issue elsewhere covering this? Not that I've spotted so far
- Which machine(s) does it work on? equinix-ubuntu2204] [591](https://ci.adoptium.net/job/Test_openjdk11_hs_sanity.external_x86-64_linux/591/)
- Which machine(s) does it fail on? ibmcloud-ubuntu1604-1 [589](https://ci.adoptium.net/job/Test_openjdk11_hs_sanity.external_x86-64_linux/589/) [592](https://ci.adoptium.net/job/Test_openjdk11_hs_sanity.external_x86-64_linux/592/) [593](https://ci.adoptium.net/job/Test_openjdk11_hs_sanity.external_x86-64_linux/593/) ibm-cloud-rhel7-1 [590](https://ci.adoptium.net/job/Test_openjdk11_hs_sanity.external_x86-64_linux/590/)

Any other details: may be related to the OS - Ubuntu 16.04 is obviously quite old. RHEL7 may have other limitations as the docker host used for these images. Since I'm not sure this has been previously reported it may be worth checking if the underlying images used for this have been updated to later versions of OSs that might be incompatible with newer containers.

Start with the linked Test_openjdk11_hs_sanity.external_x86-64_linux jobs and the Grinder rerun link, comparing failures on ibmcloud-ubuntu1604-1 and ibm-cloud-rhel7-1 with the passing equinix-ubuntu2204 run. Inspect the affected machine and container image configuration; done means the cause is reproducible and a verified infrastructure remediation is identified.

Written by the indexing model from the issue text.