adoptium / adoptium/infrastructure

test-marist-sles15-s390x-3 - NoRouteToHostException

Open
#4,506 0 comments 0 reactions 0 assignees View on GitHub
arch:s390x (zLinux) provider:marist testFail
Dominant language
Python
Stars
96
Forks
106
Avg merge
1d 23h
Merged PRs (30d)
13

Description

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): Lots, including javax/management/MBeanServer/ExceptionTest.java in jdk_jmx_1 (for example).
- Recent `Test_` link to ci.adoptium.net that shows the failure: https://ci.adoptium.net/job/Test_openjdk26_hs_extended.openjdk_s390x_linux_testList_1/40/
- Specific error text (if applicable):
```
21:31:27 class java.rmi.ConnectIOException==>Exception creating connection to: 148.100.74.157; nested exception is:
21:31:27 java.net.NoRouteToHostException: No route to host
```
- **Hyperlink** to re-run in Grinder: [Grinder rerun link](&ACTIVE_NODE_TIMEOUT=10&VENDOR_TEST_DIRS=%2Ftest%2Fsystem&EXTRA_DOCKER_ARGS=&TKG_OWNER_BRANCH=adoptium%3Amaster&OPENJ9_SYSTEMTEST_OWNER_BRANCH=eclipse%3Amaster&PLATFORM=s390x_linux&GENERATE_JOBS=false&KEEP_REPORTDIR=true&PERSONAL_BUILD=false&DOCKER_REGISTRY_DIR=&ADOPTOPENJDK_REPO=https%3A%2F%2Fgithub.com%2Fadoptium%2Faqa-tests.git&RERUN_ITERATIONS=0&SETUP_JCK_RUN=false&DOCKER_REGISTRY_URL_CREDENTIAL_ID=&LABEL=&EXTRA_OPTIONS=&CUSTOMIZED_SDK_URL=https%3A%2F%2Fci.adoptium.net%2Fjob%2Fbuild-scripts%2Fjob%2Fjobs%2Fjob%2Frelease%2Fjob%2Fjobs%2Fjob%2Fjdk26u%2Fjob%2Fjdk26u-release-linux-s390x-temurin%2F9%2F%2Fartifact%2Fworkspace%2Ftarget%2FOpenJDK26U-jdk_s390x_linux_hotspot_26.0.2.1_1.tar.gz+https%3A%2F%2Fci.adoptium.net%2Fjob%2Fbuild-scripts%2Fjob%2Fjobs%2Fjob%2Frelease%2Fjob%2Fjobs%2Fjob%2Fjdk26u%2Fjob%2Fjdk26u-release-linux-s390x-temurin%2F9%2F%2Fartifact%2Fworkspace%2Ftarget%2FOpenJDK26U-testimage_s390x_linux_hotspot_26.0.2.1_1.tar.gz+https%3A%2F%2Fci.adoptium.net%2Fjob%2Fbuild-scripts%2Fjob%2Fjobs%2Fjob%2Frelease%2Fjob%2Fjobs%2Fjob%2Fjdk26u%2Fjob%2Fjdk26u-release-linux-s390x-temurin%2F9%2F%2Fartifact%2Fworkspace%2Ftarget%2FOpenJDK26U-sbom_s390x_linux_hotspot_26.0.2.1_1.json&BUILD_IDENTIFIER=&JENKINS_KEY=&ADOPTOPENJDK_BRANCH=v1.0.14.1-release&LIGHT_WEIGHT_CHECKOUT=false&USE_JRE=false&ARTIFACTORY_SERVER=&KEEP_WORKSPACE=false&USER_CREDENTIALS_ID=&JDK_VERSION=26&DOCKER_REGISTRY_URL=&ITERATIONS=1&VENDOR_TEST_REPOS=https%3A%2F%2Fgithub.com%2Fadoptium%2Ftemurin-build&JDK_REPO=&JCK_GIT_BRANCH=master&OPENJ9_BRANCH=master&OPENJ9_SHA=&JCK_GIT_REPO=&VENDOR_TEST_BRANCHES=v2026.08.01&OPENJ9_REPO=https%3A%2F%2Fgithub.com%2Feclipse-openj9%2Fopenj9.git&UPSTREAM_JOB_NAME=&CLOUD_PROVIDER=&CUSTOM_TARGET=javax%2Fmanagement%2FMBeanServer%2FExceptionTest.java&VENDOR_TEST_SHAS=&JDK_BRANCH=&LABEL_ADDITION=&ARTIFACTORY_REPO=&ARTIFACTORY_ROOT_DIR=&UPSTREAM_TEST_JOB_NUMBER=39&DOCKERIMAGE_TAG=&JDK_IMPL=hotspot&TEST_TIME=&SSH_AGENT_CREDENTIAL=&AUTO_DETECT=true&SLACK_CHANNEL=aqavit-bot&DYNAMIC_COMPILE=false&RELATED_NODES=&ADOPTOPENJDK_SYSTEMTEST_OWNER_BRANCH=adoptium%3Amaster&APPLICATION_OPTIONS=&CUSTOMIZED_SDK_URL_CREDENTIAL_ID=eclipse_temurin_bot_email_and_token&ARCHIVE_TEST_RESULTS=false&OPENJDK_SHA=&NUM_MACHINES=&TRSS_URL=&RERUN_FAILURE=false&BUILD_LIST=openjdk&USE_TESTENV_PROPERTIES=true&ADDITIONAL_ARTIFACTS_REQUIRED=&UPSTREAM_JOB_NUMBER=&STF_OWNER_BRANCH=adoptium%3Amaster&TIME_LIMIT=25&JVM_OPTIONS=&PARALLEL=None)
- Any existing issues covering this: [This issue](https://github.com/adoptium/infrastructure/issues/2807) covered the same symptom in the past. It looks like the node affected this time was disabled during the resolution of that issue, so maybe the fix wasn't ported to it? Requesting investigation.
- Machine(s) this test works on:
- Machine(s) this test fails on: test-marist-sles15-s390x-3

Any other details:

Contributor guide

Open the contributing guide

Research direction

Start with the linked CI failure for test-marist-sles15-s390x-3 and the NoRouteToHostException from javax/management/MBeanServer/ExceptionTest.java. Compare the node with infrastructure issue 2807 and use the provided Grinder rerun link to reproduce the failure. Done means the cause on this machine is identified and the test can be repeated without the routing error.

Written by the indexing model from the issue text.

Assessment

Domain
infrastructure, networking, testing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.