1142778 - OTA for Flame Kitkat 2.2, 2.1, and 2.0 builds does not download the latest Nightly builds.

Status: RESOLVED FIXED

(Release Engineering :: Applications: MozharnessCore, defect)

Description

[Martin Shuman [:Marty]]

The latest nightly builds are not available in the OTA channels for Flame Kitkat on 2.2, 2.1, and 2.0.
This appears to be the same issue as bug 1141633 for the Master branch.

The old builds currently available in the channel are:

2.2
20150309162503

2.1
20150309161206

2.0
20150309160225

Comment 1

[Peter Bylenga [:PBylenga]]

[Blocking Requested - why for this release]:
Regression that will cause smoke tests to fail.


NI on No-Jun and Ben to take a look.

Comment 2

[Gerry Chang [:gchang]]

By using today's latest build, like comment #4 in bug 1141965, device is able to detect but device still can't download the package (bug 1142778).
I tried device update by using local OTA server, my device can detect/download/uncompress package which means today's build has no problem.
The problem here is that there is no xml file in server side. That's why device can't download package.
This might need Ben's help to fix.

Gaia-Rev        572d60e0a440ee4af50bc6b6adad8876eadbdb4d
Gecko-Rev       https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/3db27b3c9298
Build-ID        20150312162502
Version         37.0
Device-Name     flame
FW-Release      4.4.2

Comment 3

[No-Jun Park [:njpark]]

I only disabled the OTA master branch, so I think there is some config related issue here.  Ben, could you take a look at this please?  Thanks!

Comment 4

[[e-mail] (:bhearsum)]

Looks like this branch is still using the broken version of mozharness, so it's still submitting to the wrong place. I pushed https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/da3e96179c42. The first nightly to build with this changeset (hopefully later today) should get things fixed up.

Comment 5

[[e-mail] (:bhearsum)]

This is fixed now as far as I can tell. Update URLs such as https://aus4.mozilla.org/update/3/B2G/37.0a2/20150120002507/flame/en-US/nightly-b2g37/Boot2Gecko%202.2.0.0-prerelease%20%28SDK%2019%29/default/default/update.xml are returned the latest kitkat builds.

Comment 6

[Mike Lien[:mlien]]

Hi Ben, v2.1 still cannot get the latest kitkat build, could you help with it again, thanks.

Comment 7

[[e-mail] (:bhearsum)]

(In reply to Mike Lien[:mlien] from comment #6)
> Hi Ben, v2.1 still cannot get the latest kitkat build, could you help with
> it again, thanks.

Ah, sorry. I forgot to update 2.0 and 2.1 with the new mozharness revision. I've done that now, the next set of nightlies should fix things up.

Comment 8

[Pi Wei Cheng [:piwei] (inactive)]

I tested with nightly builds from 3/16 and confirmed that OTA works for 2.2, but NOT on 2.1 and 2.0.

Symptoms on 2.1 & 2.0: When asked the device to check for update, it displayed that there were no updates.

v2.0 build ID 20150316000201 -> failed
v2.1 build ID 20150316001204 -> failed
v2.2 build ID 20150316002502 -> updated successfully to build ID 20150317002504

Leaving qawanted keyword to re-test after new nightlies with fix from comment 7 have landed.

Comment 9

[KTucker [:KTucker][Inactive 3/4/2016]]

Let's check this again tomorrow.

Comment 10

[Pi Wei Cheng [:piwei] (inactive)]

This issue is verified fixed on 2.0 and 2.1.

v2.0 build ID 20150317160202 -> updated successfully to build ID 20150318000203
v2.1 build ID 20150317161204 -> updated successfully to build ID 20150318001207

Comment 11

[Vincent Liu[:vliu]]

https://hg.mozilla.org/releases/mozilla-b2g34_v2_1s/rev/5fea07bd36ec

Comment 12

[Gabriela [:gaby2300]]

I am seeing this in my Flame with 3.0. base image v18D, Spark and the 20150624160209 build. When checking for updates: "No updates are found", that's why I can't update to a newer build: I'm not receiving new OTA updates since then.

Comment 13

[Peter Bylenga [:PBylenga]]

That's a different issue, we have OTA's turned off for Flame 3.0 due to a Smoketest blocker

Comment 14

[Gabriela [:gaby2300]]

Thanks Peter for letting me know! Is there a bug or some other way to follow that issue so I'll be able to know when it's fixed?

Comment 15

[Peter Bylenga [:PBylenga]]

https://bugzilla.mozilla.org/show_bug.cgi?id=1174840

Comment 16

[Gabriela [:gaby2300]]

Many thanks!