Upgrading TCK machines which are EOL

The operating systems on the following tck machines have reached EOL or will reach it shortly. I plan to upgrade them before the next release (15/04).

• jck-marist-rhel7-s390x-2
• jck-marist-ubuntu2004-s390x-3
• jck-osuosl-ubuntu2004-ppc64le-1
• jck-osuosl-ubuntu2004-ppc64le-2

I can provision a new instance in their respective vendor consoles. Following this I will need someone in Eclipse to set up the machines up to be tck ready.

changed the description

added IT-prioritylow IT-severitylow Servers statetodo team:releng labels

assigned to @pstankie

I've created the 2 machines below to replace jck-osuosl-ubuntu2004-ppc64le-1 and -2

• jck-osuosl-ubuntu2404-ppc64le-1 140.211.168.137
• jck-osuosl-ubuntu2404-ppc64le-2 140.211.168.235

I will reach out to Pawel in order to place the Eclipse key on the machines

added statewip label and removed statetodo label

The keys has been sent.

I have access to nodes. I'll start reconfiguration with ansible.

The nodes have been reconfigured and added to JIRO

• https://github.com/temurin-compliance/infrastructure/pull/80
• https://github.com/eclipse-cbi/jiro/pull/442
• https://ci.eclipse.org/temurin-compliance/computer/jck%2Dmarist%2Dubuntu2404%2Ds390x%2D1/
• https://ci.eclipse.org/temurin-compliance/computer/jck%2Dosuosl%2Dubuntu2404%2Dppc64le%2D1/
• https://ci.eclipse.org/temurin-compliance/computer/jck%2Dosuosl%2Dubuntu2404%2Dppc64le%2D2/

I've placed the Eclipse ssh key on the newly created machine

jck-marist-ubuntu2404-s390x-1 148.100.75.241

Holding off on upgrading jck-marist-rhel7-s390x-2. In the last release we had a tck test which passed only on this machine, see https://github.com/temurin-compliance/temurin-compliance/issues/696

Will see if this test passes on the new jck-marist-ubuntu2404-s390x-1 before upgrading the rhel box

This test does not pass on jck-marist-ubuntu2404-s390x-1

removed statewip label

added Awaiting Feedback label