[16/02/25] Update Java on mozmill-ci Jenkins masters and do system updates on Linux hosts for glibc issue

RESOLVED FIXED

Status

Mozilla QA
Infrastructure
RESOLVED FIXED
2 years ago
2 years ago

People

(Reporter: whimboo, Unassigned)

Tracking

Version 4

Details

(Whiteboard: [nsm])

(Reporter)

Description

2 years ago
The following two things as described in the summary have to be done.
(Reporter)

Comment 1

2 years ago
I have updated all Linux nodes for staging including Jenkins master. I will wait with updating production nodes until later today so we can be sure no regression will be introduced.
Whiteboard: [nsm]
(Reporter)

Comment 2

2 years ago
I updated all Linux nodes for the glibc fix and got them restarted - including the Jenkins master machines.

Regarding the Java updates for all slave nodes I'm unsure if an update is necessary. The only two connections Java makes on those are the ones to the Jenkins master, and then to check for updates of Java.

Michal, do you see it still crucial to get them all updated?
Flags: needinfo?(mpurzynski)
Thanks for the work here. If the application logic makes it impossible for the Java plugin/process on slaves to accept input from untrusted sources, I think that's OK to postpone the update. Seems like it's the case here.
Flags: needinfo?(mpurzynski)
(Reporter)

Comment 4

2 years ago
That is correct. To initiate a connection with the Jenkins master I have to start a specific script on the slave. No external connection can invoke a Java process.

So I will mark this bug as fixed then. Java updates I will do when I have to update all slaves the next time which should happen in May.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
Summary: [16/02/25] Update Java on all hosts and do system updates on Linux hosts for glibc issue → [16/02/25] Update Java on mozmill-ci Jenkins masters and do system updates on Linux hosts for glibc issue
You need to log in before you can comment on or make changes to this bug.