962096 - Download link at http://www.mozilla.org/en-US/firefox/channel/ doesn't provide latest version

Status: RESOLVED WORKSFORME

(Release Engineering :: Release Requests, defect)

Description

[Mekki MacAulay [:mekki] (he/him)]

Expected behavior:

When downloading Firefox Aurora from http://www.mozilla.org/en-US/firefox/channel/ the latest version in the Aurora update channel should be offered.

Observed behavior:

The version of Aurora that is offered for download at http://www.mozilla.org/en-US/firefox/channel/ is out of synch with the Aurora update channel (not sure by how much, but at least several hours).  As a result, one can download it and then immediately have to download it again via the internal updater a second time in order to get the latest version.

(Observed with Aurora.  Firefox Beta seems to do something different on install. Not sure the full range of affected links.)

Suggested change:

The links offered at http://www.mozilla.org/en-US/firefox/channel/ should be synchronized with their respective update channels such that they always offer the same version as the internal updater.

Comment 1

[Kohei Yoshino]

The link properly points the latest build, but Aurora is built daily IIRC, so an update can happen even just after download. I think this is not a bug.

Comment 2

[Mekki MacAulay [:mekki] (he/him)]

I'm quite sure that there is a sync problem (or at least a race condition) because I had another computer that had already updated to the latest version before I downloaded from the page.  It's not just a case of an update dropping between the time of the download and install (which was mere seconds).

Comment 3

[Kohei Yoshino]

Hmm, the link on the mozilla.org site is a permanent link for each Aurora version and it won't be an issue. This is probably a sync problem on mirror servers. I'm not sure it can be resolved but moving to a better product/component.

Comment 4

[Rail Aliiev [:rail]]

Looks like a dup of bug 950119

Comment 5

[Rail Aliiev [:rail]]

I misread the bug, reopening

Comment 6

[Rail Aliiev [:rail]]

<nthomas> bug 962096 might be caching

Comment 7

[Nick Thomas [:nthomas] (UTC+12)]

(In reply to Kohei Yoshino [:kohei] from comment #3)
> Hmm, the link on the mozilla.org site is a permanent link for each Aurora
> version and it won't be an issue. This is probably a sync problem on mirror
> servers. 

There are no mirror servers in play here, just ftp.m.o with it's Zeus frontend doing caching.

We're caching for an hour:
$ curl -I https://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-aurora/firefox-29.0a2.en-US.mac.dmg
HTTP/1.1 200 OK
Server: Apache
X-Backend-Server: ftp4.dmz.scl3.mozilla.com
Cache-Control: max-age=3600
Content-Type: application/x-apple-diskimage
Date: Thu, 20 Mar 2014 00:12:48 GMT
Expires: Thu, 20 Mar 2014 01:12:48 GMT
Accept-Ranges: bytes
Access-Control-Allow-Origin: *
ETag: "48f8f69-498d821-4f4c966159d41"
Last-Modified: Mon, 17 Mar 2014 08:42:25 GMT
X-Cache-Info: caching
Content-Length: 77125665

We typically do one build a day on the aurora update channel, the actual time it appears depends on the platform and locale, but you would be relatively unlucky to hit the hour when an old build would be served from the cache (more than once anyway!).

Comment 8

[Nick Thomas [:nthomas] (UTC+12)]

Mekki, it would be helpful if you could do this:

1, download an Aurora build from the channel page (preferably using 'wget -S', or 'curl -i' so we can see headers, but in a browser would be OK)
2, in about:config, set app.update.log to true
3, force an update check by going to About Firefox
4, if an update is found then open Tools > Web Developer > Browser Console and look for a message containing 'AUS:SVC Checker:checkForUpdates'.

Report back headers (if available) and the AUS log line. Thanks!

Comment 9

[Nick Thomas [:nthomas] (UTC+12)]

Now isn't a good time to test though, as the Aurora updates are frozen on the last v29.0 build. Once QA signs off the v30 code that came from Nightly updates will come out ~ once a day again. That should be early next week.

Comment 10

[Rail Aliiev [:rail]]

At the moment we use Bouncer links on that page. Bouncer redirects to CDNs. We may have more fun now :)

Comment 11

[Rail Aliiev [:rail]]

I haven't heard any issues after we switched to using CDNs/S3.

Comment 12

[Mekki MacAulay [:mekki] (he/him)]

Why INCOMPLETE as the resolution?  If the solution was switching to using CDNs/S3, wouldn't that be RESOLVED->FIXED?

Comment 13

[Rail Aliiev [:rail]]

(In reply to Mekki MacAulay [:mekki] from comment #12)
> Why INCOMPLETE as the resolution?  If the solution was switching to using
> CDNs/S3, wouldn't that be RESOLVED->FIXED?

I'm not quite sure if it's fixed. That's the only reason. Probably WORKSFORME is better in this case. :)