Hello,
After today's CentOS CI OCP maintenance all our Jenkins jobs are stuck in a queue. After closer look in the OCP console all cico-workspace pods seem to fail due to:
OPENSHIFT_JENKINS_JVM_ARCH='', CONTAINER_MEMORY_IN_MB='8796093022207', using /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.322.b06-11.el8.x86_64/jre/bin/java Downloading http://172.30.254.125: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 -cp /home/jenkins/remoting.jar hudson.remoting.jnlp.Main -headless -url http://172.30.254.125:80/ -tunnel 172.30.191.143:50000 3e4fe1de113a538c80088d43a7647162c0baabcd5117c7bdaa0bc2912aa1074e cico-workspace-5vbmk Error: A JNI error has occurred, please check your installation and try again 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 at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:756) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) at java.net.URLClassLoader.defineClass(URLClassLoader.java:473) at java.net.URLClassLoader.access$100(URLClassLoader.java:74) at java.net.URLClassLoader$1.run(URLClassLoader.java:369) at java.net.URLClassLoader$1.run(URLClassLoader.java:363) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:362) at java.lang.ClassLoader.loadClass(ClassLoader.java:418) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352) at java.lang.ClassLoader.loadClass(ClassLoader.java:351) at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:601) 2023/05/02 07:33:30 [go-init] Main command failed 2023/05/02 07:33:30 [go-init] exit status 1 2023/05/02 07:33:30 [go-init] No post-stop command defined, skip
So I guess the cico-workspace image needs to be updated?
Metadata Update from @dkirwan: - Issue assigned to dkirwan
Arrfab kicked off a rebuild of the cico-workspace image, that seems to have resolved this issue, can you confirm @mrc0mmand ?
cico-workspace
Metadata Update from @dkirwan: - Issue assigned to arrfab (was: dkirwan)
Yup, can confirm that all our jobs are up and running again, thanks!
Metadata Update from @dkirwan: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.