987425 - No update served while aurora update frozen

Status: RESOLVED FIXED

(Release Engineering Graveyard :: Applications: Balrog (backend), defect)

Description

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

With aurora pointing at Fennec-mozilla-aurora-nightly-20140317004002, and auroratest at Fennec-mozilla-aurora-nightly-latest (i.e. before re-enabling Aurora updates)

# wut, no update
https://aus4.mozilla.org/update/4/Fennec/29.0a1/20140313030202/Android_arm-eabi-gcc3/en-US/aurora/4.4.2/default/default/30.0a1/update.xml
<?xml version="1.0"?>
<updates>
</updates>

# meanwhile on auroratest
https://aus4.mozilla.org/update/4/Fennec/29.0a1/20140313030202/Android_arm-eabi-gcc3/en-US/auroratest/4.4.2/default/default/30.0a1/update.xml
<?xml version="1.0"?>
<updates>
    <update type="minor" version="30.0a2" extensionVersion="30.0a2" buildID="20140324150430">
        <patch type="complete" URL="http://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/2014/03/2014-03-24-15-04-30-mozilla-aurora-android/fennec-30.0a2.multi.android-arm.apk" hashFunction="sha512" hashValue="c71c0d53339f2965736ec6e3286fbfb49648aab41fc22db2cf4419c223e39dfff9a5ba7f9986d45070e5e7524aa5aebda27ef241bf413986eaed0dce1b81b511" size="32704962"/>
    </update>
</updates>


Set aurora to point at Fennec-mozilla-aurora-nightly-latest, and check same aurora url as before:
https://aus4.mozilla.org/update/4/Fennec/29.0a2/20140313030202/Android_arm-eabi-gcc3/en-US/aurora/4.4.2/default/default/30.0a1/update.xml
<?xml version="1.0"?>
<updates>
    <update type="minor" version="30.0a2" extensionVersion="30.0a2" buildID="20140324150430">
        <patch type="complete" URL="http://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/2014/03/2014-03-24-15-04-30-mozilla-aurora-android/fennec-30.0a2.multi.android-arm.apk" hashFunction="sha512" hashValue="c71c0d53339f2965736ec6e3286fbfb49648aab41fc22db2cf4419c223e39dfff9a5ba7f9986d45070e5e7524aa5aebda27ef241bf413986eaed0dce1b81b511" size="32704962"/>
    </update>
</updates>

Should have been offering the 20140317004002 build on aurora before hand.

Comment 1

[[e-mail] (:bhearsum)]

Looking at the blob (https://aus4-admin.mozilla.org/releases/Fennec-mozilla-aurora-nightly-20140317004002/data) I only see Android_x86-gcc3 in it.

Looked at a log and saw:
Starting new HTTPS connection (3): aus4-admin.mozilla.org
"PUT /releases/Fennec-mozilla-central-nightly-20140317030202/builds/Android_arm-eabi-gcc3/en-US HTTP/1.1" 401 79
Caught HTTPError: ffxbld is not allowed to access /releases/:name/builds/:platform/:locale by PUT

So, these got caught up in the fallout from bug 749297. https://bugzilla.mozilla.org/show_bug.cgi?id=984163#c11 says that I was able to resubmit x86 Aurora by hand, which explains why it was there but not other platforms.

In the future, we should probably avoid freezing at a build with missing platforms, or maybe create a new blob with the the latest possible build for each platform. I'm not sure if there's anything better we can do it in balrog/nightly build automation to make this less painful in the future...

Comment 2

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

If we had automation for the freezing we could do a sanity check for having all platforms and locales in the blob, but that's going to be hard to do with an eyeball except for Android. I think we should just take this as a once-off bustage. Thanks for the debugging!