Closed Bug 627598 Opened 13 years ago Closed 13 years ago

Some old-style universal releases on the 4.0-line appear to be stranded

Categories

(Release Engineering :: General, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: u279076, Assigned: bhearsum)

References

Details

Attachments

(3 files)

Major updates for 3.7a1 through 4.0b7 do not seem to be working. Check For Updates returns 4.0b8. Trying to download that update results in the updater failing to connect to the server.
Please specify which flavour of mac builds you are testing with (documented in bug 626815 comment #2). Anything from a5 to b6 is ambiguous.
All builds taken from their respective folders here:
ftp://ftp.mozilla.org/pub/firefox/releases/

The builds specifically are:

32-bit builds
-------------
* 3.7a1 en-US
* 3.7a2 en-US
* 3.7a3 en-US
* 3.7a4 en-US
* 3.7a5 en-US
* 4.0b1 en-US
* 4.0b2 en-US + nl
* 4.0b3 en-US + fi
* 4.0b4 en-US + es-ES
* 4.0b5 en-US + ko
* 4.0b6 en-US + ja-JP-mac
* 4.0b7 en-US + ja-JP-mac

64-bit builds
-------------
* 3.7a5 en-US
* 4.0b1 en-US
* 4.0b2 en-US
* 4.0b3 en-US + zh-TW
* 4.0b4 en-US + ja-JP-mac
* 4.0b5 en-US + da
* 4.0b6 en-US + ja-JP-mac
* 4.0b7 en-US + ja-JP-mac
I tried the 4.0b7 en-US universal. It hit https://aus3.mozilla.org/update/3/Firefox/4.0b7/20101104131842/Darwin_x86_64-gcc3-u-i386-x86_64/en-US/releasetest/Darwin%2010.6.0/default/default/update.xml?force=1 and got offered 4.0b9. BUT as the details page is not up it looks a lot like a minor update, just with the major update buttons. Screenshots to follow.
Attached image releasetest - offer
Presumably the code has fallen back to a non-billboard when mozilla.com returns a 404.
After retesting, it seems that B7 is ok...all other versions listed before are busted.
(In reply to comment #5)
> Created attachment 505660 [details]
> releasetest - offer
> 
> Presumably the code has fallen back to a non-billboard when mozilla.com returns
> a 404.
That is correct and was implemented in bug 548061
(In reply to comment #9)
> I just tested on B6 and everything appeared to work fine
> 
> AUS:SVC Checker:getUpdateURL - update URL:
> https://aus2.mozilla.org/update/3/Firefox/4.0b6/20100914073111/Darwin_x86_64-gcc3/en-US/releasetest/Darwin%2010.6.0/default/default/update.xml?force=1

Confirmed.  B6 64bit is working, B6 32bit is not.
I've done some further testing.  Looks like it's just the 32-bit builds; anything from B6 or earlier.  For those of you not following along, it's these builds which are failing to update:

* 3.7a1 en-US 32-bit
* 3.7a2 en-US 32-bit 
* 3.7a3 en-US 32-bit
* 3.7a4 en-US 32-bit
* 3.7a5 en-US 32-bit
* 4.0b1 en-US 32-bit
* 4.0b2 en-US 32-bit
* 4.0b2 nl 32-bit 
* 4.0b3 en-US 32-bit
* 4.0b3 fi 32-bit
* 4.0b4 ko 32-bit
* 4.0b4 es-ES 32-bit
* 4.0b5 en-US 32-bit
* 4.0b5 ko 32-bit
* 4.0b6 en-US 32-bit
* 4.0b6 ja-JP-mac 32-bit
To reiterate, 64-bit builds are OK, 32-bit builds B6 and earlier are NOT.
Could you toggle the app.update.log preference so it is true and restart. Then open the error console, clear it, and check for updates. Find the entry that starts with "AUS:SVC Checker:getUpdateURL - update URL:" and paste it in this bug.
(In reply to comment #12)
> To reiterate, 64-bit builds are OK, 32-bit builds B6 and earlier are NOT.

Around the time we shipped Beta 8, we decided to stop providing direct updates for users old universal -> the latest new universal, so it's expected that 32-bit B6 builds aren't receiving the Major Update.

However, they should be receiving a minor update to Beta 8. I'll look into why they aren't.
Assignee: nobody → bhearsum
Summary: Major Update for 4.0b9 fail for Mac → Some old-style universal releases on the 4.0-line appear to be stranded
Looks like the issue with the old-style universals is that Bouncer has almost no uptake for Beta 8. This is probably fallout from changes we made to the push to mirror setup last month. I'm going to consult with IT on what we should be doing.
(In reply to comment #15)
> Looks like the issue with the old-style universals is that Bouncer has almost
> no uptake for Beta 8. This is probably fallout from changes we made to the push
> to mirror setup last month. I'm going to consult with IT on what we should be
> doing.

I re-added 4.0b8 to the mozilla-releases rsync module and we should be back in business here. Anthony, do you want to confirm?
Looks like we are ok now.  Feel free to call this resolved fixed.
Thanks for finding and verifying the fix here Anthony!
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
bug 628182 talks about one of our internal mirrors being misconfigured for DMG/MAR files, which is probably why these updates started breaking in the first place. With that fixed I'm going to drop 4.0b8 from the mozilla-releases module again, and we *should* still be OK here.
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: