Details
Major Description
Description of problem:
Customer facing issue with jenkins on Openshift : openshift4/ose-jenkins-agent-base node images v4.10 not able to communicate with openshift4/ose-jenkins v4.10.0
Version-Release number of selected component (if applicable):
4.10.0
How reproducible:
Always
Steps to Reproduce:
1. 2. 3.
Actual results:
During agent connection received : Exception in thread "main" java.lang.UnsupportedClassVersionError: hudson/remoting/jnlp/Main has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0
Expected results:
OPENSHIFT_JENKINS_JVM_ARCH='', CONTAINER_MEMORY_IN_MB='4096', using /usr/lib/jvm/java-11-openjdk-11.0.19.0.7-1.el8_7.x86_64/bin/java Downloading http://controller.ocp050014.svc:80/jnlpJars/remoting.jar ... + cd + exec java -Duser.home=/home/jenkins -Dcom.redhat.fips=false -XX:+UseParallelGC -XX:MinHeapFreeRatio=5 -XX:MaxHeapFreeRatio=10 -XX:GCTimeRatio=4 -XX:AdaptiveSizePolicyWeight=90 -Xmx2048m -cp /home/jenkins/remoting.jar hudson.remoting.jnlp.Main -headless -url http://controller.ocp050014.svc:80/ -tunnel controller-jnlp.ocp050014.svc:50000 XXX ci-automation-tools-j529v Apr 25, 2023 11:20:42 AM hudson.remoting.jnlp.Main createEngine INFO: Setting up agent: ci-automation-tools-j529v Apr 25, 2023 11:20:42 AM hudson.remoting.Engine startEngine INFO: Using Remoting version: 3044.vb_940a_a_e4f72e Apr 25, 2023 11:20:42 AM hudson.remoting.Engine startEngine WARNING: No Working Directory. Using the legacy JAR Cache location: /home/jenkins/.jenkins/cache/jars Apr 25, 2023 11:20:42 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Locating server among [http://controller.ocp050014.svc:80/] Apr 25, 2023 11:20:42 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve INFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping] Apr 25, 2023 11:20:42 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve INFO: Remoting TCP connection tunneling is enabled. Skipping the TCP Agent Listener Port availability check Apr 25, 2023 11:20:42 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Agent discovery successful Agent address: controller-jnlp.ocp050014.svc Agent port: 50000 Identity: 20:1a:e9:55:d5:a6:a1:91:b9:7a:43:de:e0:0b:c9:04 Apr 25, 2023 11:20:42 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Handshaking Apr 25, 2023 11:20:42 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Connecting to controller-jnlp.ocp050014.svc:50000 Apr 25, 2023 11:20:42 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Trying protocol: JNLP4-connect Apr 25, 2023 11:20:42 AM org.jenkinsci.remoting.protocol.impl.BIONetworkLayer$Reader run INFO: Waiting for ProtocolStack to start. Apr 25, 2023 11:20:42 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Remote identity confirmed: 20:1a:e9:55:d5:a6:a1:91:b9:7a:43:de:e0:0b:c9:04 Apr 25, 2023 11:20:42 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Connected
Additional info:
From customer: for now we’ve tested v4.10, v4.11, v4.12 agent base image with this image. With 4.10 we encounter java ver issue 4.11 and 4.12 generates issues with template compatibility we are using.
