On 32.0.3, offered nonexistant update



5 years ago
5 years ago


(Reporter: aaronmt, Unassigned)


Firefox Tracking Flags

(Not tracked)



(1 attachment)



5 years ago
Posted file update.log
See log

Comment 1

5 years ago
Comment on attachment 8501978 [details]

3:52  bhearsum:	 this is a release channel test
03:52  bhearsum: https://aus3.mozilla.org/update/3/Firefox/32.0.3/20140923175406/Darwin_x86_64-gcc3-u-i386-x86_64/en-US/release/Darwin%2013.4.0/default/default/update.xml?force=1
03:52  bhearsum:	 i think i pushed the wrong snippets....
03:52  bhearsum:	 i'm shutting off updates while i clean up
Attachment #8501978 - Attachment mime type: text/x-log → text/plain

Comment 2

5 years ago
This is now resolved, see R-D.
Last Resolved: 5 years ago
Resolution: --- → FIXED
For posterity:
This is fixed up now. Nobody was actually updated, because the update responses pointed to files that didn't exist on the CDN yet, but some users did receive an update dialog that resulted in a failed update.
As Andreas says, we should talk about this in the post mortem, but I do want to mention that the new update server that we're pushing live in a couple of weeks should reduce this kind of human error, and we have plans to integrate these
+pushes with Ship It, which should make it even more difficult to mess this up.
Thank you very much to AaronMT and others for catching this so quickly, and to Nick and Rail for helping me fix things up - I owe you all a few.

- Ben

On Wed, Oct 08, 2014 at 03:56:56PM -0400, Ben Hearsum wrote:
> Hey folks,
> When the go for Firefox 33.0 RC to the beta channel came I accidentally pushed it live for the release channel in addition to beta. This means that for just over an hour starting at 2:35pm Eastern, Firefox 33.0 updates were live for the
+release channel. I've since shut off the updates on the release channel completely until I can rectify my mistake.
> Very sorry about this.
> - Ben

And https://wiki.mozilla.org/Releases/Firefox_33.0/BuildNotes#Undo_accidental_push has the details on how I fixed things up, with Rail and Nick's help.
You need to log in before you can comment on or make changes to this bug.