Closed Bug 1020119 Opened 10 years ago Closed 10 years ago

Update mozmill-ci machines to Java 7 update 60, latest Flash and MS security updates on related node

Categories

(Mozilla QA Graveyard :: Infrastructure, defect)

Product:
Mozilla QA Graveyard
Component:
Infrastructure
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: whimboo, Assigned: danisielm)

Details

Oracle has released Java 7 update 60:
http://www.oracle.com/technetwork/java/javase/7u60-relnotes-2200106.html

We might want to update our nodes for that version.

Maybe we should wait until Adobe and MS also offer their monthly updates, and do all at once.
We have Flash updates as well:
http://helpx.adobe.com/en/flash-player/release-note/fp_14_air_14_release_notes.html

And please check security updates on Windows too, we should start with those machines.
Assignee: nobody → cosmin.malutan
Status: NEW → ASSIGNED
Summary: Update mozmill-ci machines to Java 7 update 60 → Update mozmill-ci machines to Java 7 update 60, latest Flash and MS security updates on related node
We should also update the Linux boxes for OS updates, which we would have to do anyway to get the Flash player upgrade. But also please check for updates on OS X. Maybe it's the last time we have to do this manually!
I updated all staging nodes.
On production I updated windows 7 x86 & x64 nodes and windows 8.1 x86.
I would like that someone else continuous on this task. Reason is the following:

* Production machines have been updated right after the staging ones, which is not allowed. Especially not when we have release tests to do on that day, here nearly the same time.
* On the Windows machines it looks like the release version of Flash has been installed, while it should be the debug version. That's why we see the crashes
* The new version of Java has been installed, but the old one has not been uninstalled. I assume the script has not been updated.

Not sure what else might have gone wrong here for the other platform, but given that all is well documented all that should not have happened.

Andreea, who can take over?
Assignee: cosmin.malutan → nobody
Given that investigation I reinstalled Flash on staging with the debug version. On production I downgraded Flash on all the affected nodes from 14.0.x.x to 13.0.0.124 debug. All the other software I cannot downgrade. But I think that should be ok.
Also on OS X any mounted DMG file for updates was not unmounted, and a modal dialog was visible that the installed has been succeeded.
Daniel will take over as he updated patches on most of his bugs, waiting reviews and will be duty next week.
Assignee: nobody → daniel.gherasim
Today updated this nodes:

NODE - JAVA/FLASH/OS

mm-osx-106-1 - NA / NA / Updated
mm-osx-106-2 - NA / NA / Updated
mm-osx-106-3 - NA / NA / Updated
mm-osx-106-4 - NA / NA / Updated

mm-osx-107-1 - Java 7u60 / Updated to 14.0.0.125 / Updated
mm-osx-107-2 - Java 7u60 / Updated to 14.0.0.125 / Updated
mm-osx-107-3 - Java 7u60 / Updated to 14.0.0.125 / Updated
mm-osx-107-4 - Java 7u60 / Updated to 14.0.0.125 / Updated
I've made some more updates today :

mm-osx-108-1 - Java 7u60 / Updated to 14.0.0.125 / Updated
mm-osx-108-2 - Java 7u60 / Updated to 14.0.0.125 / Updated
mm-osx-108-3 - Java 7u60 / Updated to 14.0.0.125 / Updated
mm-osx-108-4 - Java 7u60 / Updated to 14.0.0.125 / Updated

mm-osx-109-1 - / /
mm-osx-109-2 - Java 7u60 / Updated to 14.0.0.125 / Updated
mm-osx-109-3 - Java 7u60 / Updated to 14.0.0.125 / Updated
mm-osx-109-4 - Rebooted because it was unresponsive through VNC

mm-ub-1204-32-1 - / /
mm-ub-1204-32-2 - Java 7u60 / 11,2,202,378  / Updated
mm-ub-1204-32-3 - Java 7u60 / 11,2,202,378  / Updated
mm-ub-1204-32-4 - Java 7u60 / 11,2,202,378  / Updated

mm-ub-1204-64-1 - / /
mm-ub-1204-64-2 - Java 7u60 / 11,2,202,378  / Updated
mm-ub-1204-64-3 - Java 7u60 / 11,2,202,378  / Updated
mm-ub-1204-64-4 - Java 7u60 / 11,2,202,378  / Updated
Only windows nodes remained.

mm-osx-109-1 - Java 7u60 / Updated to 14.0.0.125 / Updated
mm-osx-109-4 - Java 7u60 / Updated to 14.0.0.125 / Updated

mm-ub-1204-32-1 - Java 7u60 / 11,2,202,378  / Updated
mm-ub-1204-32-2 - Checked
mm-ub-1204-32-3 - Checked
mm-ub-1204-32-4 - Checked

mm-ub-1204-64-1 - Java 7u60 / 11,2,202,378  / Updated
mm-ub-1204-64-2 - Checked
mm-ub-1204-64-3 - Checked
mm-ub-1204-64-4 - Checked

mm-ub-1310-32-1 - Java 7u60 / 11,2,202,378  / Updated
mm-ub-1310-32-2 - Java 7u60 / 11,2,202,378  / Updated
mm-ub-1310-32-3 - Java 7u60 / 11,2,202,378  / Updated
mm-ub-1310-32-4 - Java 7u60 / 11,2,202,378  / Updated

mm-ub-1310-64-1 - Java 7u60 / 11,2,202,378  / Updated
mm-ub-1310-64-2 - Java 7u60 / 11,2,202,378  / Erors while updating :

> Errors were encountered while processing:
>  udev
>  systemd-services
>  libpam-systemd:amd64
>  indicator-datetime
>  gnome-control-center-datetime
>  udisks
>  udisks2
>  usb-creator-common
>  usb-creator-gtk
>  xserver-xorg-core
>  xserver-xorg-video-intel
>  xserver-xorg-video-openchrome
> E: Sub-process /usr/bin/dpkg returned an error code (1)

Restarted node & it didn't came back.
Filed bug 1026975 for this.

mm-ub-1310-64-3 - Java 7u60 / 11,2,202,378  / Updated
mm-ub-1310-64-4 - Java 7u60 / 11,2,202,378  / Updated
Done some more updates here on some machines I could catch free.

For windows there were already new updates, 1 marked as important.
Also Java reinstalled. Looks like it was not installed using the script.

mm-win-7-32-2 - Java 7u60 / 14.0.0.125 debug / Updated
mm-win-7-32-3 - Java 7u60 / 14.0.0.125 debug / Updated
mm-win-7-32-4 - Java 7u60 / 14.0.0.125 debug / Updated

On the x64 nodes, after installing java using the script & deleting the c:/jenkins folder, I couldn't open jenkins using the shortcut on the desktop, opened it from browser.

mm-win-7-64-1 - Java 7u60 / 14.0.0.125 debug / Updated
mm-win-7-64-3 - Java 7u60 / 14.0.0.125 debug / Updated
(In reply to daniel.gherasim from comment #11)
> Also Java reinstalled. Looks like it was not installed using the script.

Why it was not installed by the script? You didn't mention anything on IRC. We cannot continue with custom processes each individual will handle differently. We have to rely on the scripts we use for updating the system. So this is critical in terms of what was wrong. For me all was fine by last week and I have not seen any problems. So please come back with details of those failures.

> On the x64 nodes, after installing java using the script & deleting the
> c:/jenkins folder, I couldn't open jenkins using the shortcut on the
> desktop, opened it from browser.

Have you checked the shortcut? Does it need an update? Please don't do workaround with the browser. As said above we have to rely on code to get stuff done.
(In reply to Henrik Skupin (:whimboo) from comment #12)
> (In reply to daniel.gherasim from comment #11)
> > Also Java reinstalled. Looks like it was not installed using the script.
> 
> Why it was not installed by the script? You didn't mention anything on IRC.
> We cannot continue with custom processes each individual will handle
> differently. We have to rely on the scripts we use for updating the system.
> So this is critical in terms of what was wrong. For me all was fine by last
> week and I have not seen any problems. So please come back with details of
> those failures.
> 

There was no failure, just that the checkbox for updating java was checked (that means  the registry file was not run), and this was present only on some of the machines (maybe the ones were updated here).
So my assumption was that java was not installed using the script.
I remember I told you about this on IRC, reinstalled now using the script & it should be fine

> > On the x64 nodes, after installing java using the script & deleting the
> > c:/jenkins folder, I couldn't open jenkins using the shortcut on the
> > desktop, opened it from browser.
> 
> Have you checked the shortcut? Does it need an update? Please don't do
> workaround with the browser. As said above we have to rely on code to get
> stuff done.

Checked, I'm updating the shortcut where it's needed.
(In reply to daniel.gherasim from comment #13)
> I remember I told you about this on IRC, reinstalled now using the script &
> it should be fine

It should be fine, or do you have checked that setting on the boxes after the installation? Thats important.
(In reply to Henrik Skupin (:whimboo) from comment #14)
> (In reply to daniel.gherasim from comment #13)
> > I remember I told you about this on IRC, reinstalled now using the script &
> > it should be fine
> 
> It should be fine, or do you have checked that setting on the boxes after
> the installation? Thats important.

I surely did.
Finished all updates. We are fine now on all machines.

NODE - JAVA/FLASH/OS
mm-win-7-32-1 - Java 7u60 / 14.0.0.125 debug / Updated

mm-win-7-64-2 - Java 7u60 / 14.0.0.125 debug / Updated
mm-win-7-64-4 - Java 7u60 / 14.0.0.125 debug / Updated

mm-win-81-32-1 - Java 7u60 / 14.0.0.125 debug / Updated
mm-win-81-32-2 - Java 7u60 / 14.0.0.125 debug / Updated
mm-win-81-32-3 - Java 7u60 / 14.0.0.125 debug / Updated
mm-win-81-32-4 - Java 7u60 / 14.0.0.125 debug / Updated

mm-win-81-64-1 - Java 7u60 / 14.0.0.125 debug / Updated
mm-win-81-64-2 - Java 7u60 / 14.0.0.125 debug / Updated
mm-win-81-64-3 - Java 7u60 / 14.0.0.125 debug / Updated
mm-win-81-64-4 - Java 7u60 / 14.0.0.125 debug / Updated

mm-win-8-32-1 - Java 7u60 / 14.0.0.125 debug / Updated
mm-win-8-32-2 - Java 7u60 / 14.0.0.125 debug / Updated
mm-win-8-32-3 - Java 7u60 / 14.0.0.125 debug / Updated
mm-win-8-32-4 - Java 7u60 / 14.0.0.125 debug / Updated

mm-win-8-64-1 - Java 7u60 / 14.0.0.125 debug / Updated
mm-win-8-64-2 - Java 7u60 / 14.0.0.125 debug / Updated
mm-win-8-64-3 - Java 7u60 / 14.0.0.125 debug / Updated
mm-win-8-64-4 - Java 7u60 / 14.0.0.125 debug / Updated

mm-win-vista-32-1 - Java 7u60 / 14.0.0.125 debug / Updated
mm-win-vista-32-2 - Java 7u60 / 14.0.0.125 debug / Updated
mm-win-vista-32-3 - Java 7u60 / 14.0.0.125 debug / Updated
mm-win-vista-32-4 - Java 7u60 / 14.0.0.125 debug / Updated

mm-win-xp-32-1 - Java 7u60 / 14.0.0.125 / Updated
mm-win-xp-32-2 - Java 7u60 / 14.0.0.125 / Updated
mm-win-xp-32-3 - Java 7u60 / 14.0.0.125 / Updated
mm-win-xp-32-4 - Java 7u60 / 14.0.0.125 / Updated
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
The update of Java to version 7u60 might have been caused the following issue in CI:
https://github.com/mozilla/mozmill-ci/issues/510
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.