Project

General

Profile

action #116539

jenkins.qa.suse.de not reachable and not triggering tests like krypton anymore

Added by okurz 2 months ago. Updated 2 months ago.

Status:
Resolved
Priority:
Urgent
Assignee:
Target version:
Start date:
2022-09-14
Due date:
% Done:

0%

Estimated time:

Description

Observation

This was observed by members of the tools team 2022-09-12 and confirmed by dimstar in https://suse.slack.com/archives/C02CANHLANP/p1663138998907489


Related issues

Copied to openQA Infrastructure - action #116689: Do not rely on statically configured IPv4 addresses for the salt master in /etc/hosts size:SResolved2022-09-14

History

#1 Updated by okurz 2 months ago

  • Status changed from New to In Progress

Error in journalctl -e -u jenkins says:

Sep 14 09:06:18 qajenkins jenkins[2092]: Sep 14, 2022 9:06:18 AM executable.Main verifyJavaVersion
Sep 14 09:06:18 qajenkins jenkins[2092]: SEVERE: Running with Java class version 52, which is older than the Minimum required version 55. See https://jenkin>
Sep 14 09:06:18 qajenkins jenkins[2092]: java.lang.UnsupportedClassVersionError: 52.0
Sep 14 09:06:18 qajenkins jenkins[2092]:         at executable.Main.verifyJavaVersion(Main.java:145)
Sep 14 09:06:18 qajenkins jenkins[2092]:         at executable.Main.main(Main.java:109)
Sep 14 09:06:18 qajenkins jenkins[2092]: Jenkins requires Java versions [17, 11] but you are running with Java 1.8 from /usr/lib64/jvm/java-1.8.0-openjdk-1.>
Sep 14 09:06:18 qajenkins jenkins[2092]: java.lang.UnsupportedClassVersionError: 52.0
Sep 14 09:06:18 qajenkins jenkins[2092]:         at executable.Main.verifyJavaVersion(Main.java:145)
Sep 14 09:06:18 qajenkins jenkins[2092]:         at executable.Main.main(Main.java:109)

upgrading to Leap 15.4 first.

#2 Updated by okurz 2 months ago

  • Status changed from In Progress to Resolved

Conducted upgrade to Leap 15.4

zypper --releasever=15.4 ref && zypper --releasever=15.4 -n --no-refresh dup --auto-agree-with-licenses --replacefiles --download-in-advance --dry-run

and then installed more recent version of Java and service restart with

zypper -n in java-17-openjdk
systemctl restart jenkins

Then webUI of jenkins was reachable again. Then I opened
http://jenkins.qa.suse.de/updateCenter/ to install all pending updates. I also triggered runs of gnome_next-openqa and trigger-openQA_in_openQA-TW which both went fine.

To add the machine to monitoring I did the following changes

echo '10.160.0.207    salt' >> /etc/hosts
echo jenkins.qa.suse.de > /etc/salt/minion_id
systemctl enable --now salt-minion

and accept and apply salt from the master osd:

sudo salt-key -y -a jenkins.qa.suse.de
sudo salt 'jenkins*' state.apply test=True
sudo salt 'jenkins*' state.apply
sudo salt -C 'G@roles:monitor' state.apply

And now https://monitor.qa.suse.de/d/GDjenkins/dashboard-for-jenkins?orgId=1&refresh=1m shows monitoring results from jenkins.qa.suse.de

There was a problem with the hostname fixed in https://gitlab.suse.de/qa-sle/qanet-configs/-/merge_requests/41/diffs?commit_id=96dedfcafaf079b0b0a94f8d52f9b3b9afc18032

#3 Updated by okurz 2 months ago

  • Copied to action #116689: Do not rely on statically configured IPv4 addresses for the salt master in /etc/hosts size:S added

Also available in: Atom PDF