Adam Alldredge [:AdamA][Inactive] Reporter
	Description • 9 years ago

Description:
If the user is attempting to update the phone via the internet no updates will be found, if the user manually checks in the system information there will be an error message that appears. The error message says "There was an error when checking for updates."

Repro Steps:
1) Update a Aries to 20151028104739
2) Go to settings > Device Information
3) Press the "Check Now" button
4) Observe messaging under button

Actual:
There was an error when checking for phone updates

Expected:
It is expected that the user is able to successfully check for updates.

Environmental Variables:
Device: Aries 2.5 [Full Flash]
Build ID: 20151028104739
Gaia: 2e89362de40a6c9c36525d36317fa1ae8e67e143
Gecko: fc706d376f0658e560a59c3dd520437b18e8c4a4
Gonk: 2916e2368074b5383c80bf5a0fba3fc83ba310bd
Version: 44.0a1 (2.5)
Firmware Version: D5803_23.1.A.1.28_NCB.ftf
User Agent: Mozilla/5.0 (Mobile; rv:44.0) Gecko/44.0 Firefox/44.0

Repro frequency: 10/10
Link to failed test case: https://moztrap.mozilla.org/manage/case/2313/
See attached: screenshot, logcat

	Adam Alldredge [:AdamA][Inactive] Reporter
	Comment 2 • 9 years ago

This issue DOES occur on Flame 2.5.

Environmental Variables:
Device: Flame 2.5 [Full Flash]
BuildID: 20151028030421
Gaia: 2e89362de40a6c9c36525d36317fa1ae8e67e143
Gecko: fc706d376f0658e560a59c3dd520437b18e8c4a4
Gonk: 205ac4204bbbb2098a8046444acba551ba5dc75a
Version: 44.0a1 (2.5) 
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:44.0) Gecko/44.0 Firefox/44.0

Result:
There was an error when checking for phone updates.
------------------------------------------------
This issue DOES NOT occur on Flame 2.2.

Environmental Variables:
Device: Flame 2.2 [Full Flash]
BuildID: 20151028032502
Gaia: 885647d92208fb67574ced44004ab2f29d23cb45
Gecko: 05144e035522
Gonk: bd9cb3af2a0354577a6903917bc826489050b40d
Version: 37.0 (2.2) 
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0

Result:
User is able to check for updates successfully.

	KTucker [:KTucker][Inactive 3/4/2016]
	Comment 3 • 9 years ago

[Blocking Requested - why for this release]:

Regression and breakage of a major functionality.

	Naoki Hirata :nhirata (please use needinfo instead of cc)
	Comment 4 • 9 years ago

https://aus5.mozilla.org/update/5/B2G/44.0a1/20151010104739/aries/en-US/dogfood/Boot2Gecko%202.5.0.0-prerelease%20%28SDK%2019%29/default/default/d0e3d5a734684c30aa3bd36699aab2805f032b670b3c73c73413c1abd58719723f52b0c26e6f239a7bd9c643654283bd9d9ae7344578673baa0aefc930d3c34b/update.xml?force=1

Changed the date that was on the buildid.

The issue is that the buildid you are on and the buildid that is on latest currently is the same so you won't see an update.  I think we should change this bug so that it gives better messaging for builds that are on the current build.  It might have gotten broken due to some of the changes we are making to accommodate IMEI whitelisting FOTA.

	Pi Wei Cheng [:piwei] (inactive)
	Comment 5 • 9 years ago

We're no longer seeing this issue and while it reproduced it was reproducing all the way back to 10/1 so we suspected it's a server side issue.

	Pi Wei Cheng [:piwei] (inactive)
	Comment 6 • 9 years ago

on a 10/27 aries build, the following URL worked on getting a system update:
https://aus5.mozilla.org/update/5/%PRODUCT%/%VERSION%/%BUILD_ID%/%PRODUCT_DEVICE%/%LOCALE%/%CHANNEL%/%OS_VERSION%/%DISTRIBUTION%/%DISTRIBUTION_VERSION%/%IMEI%/update.xml

	Pi Wei Cheng [:piwei] (inactive)
	Comment 7 • 9 years ago

Comment 6 is the update channel URL in dev settings. When I looked at logcat it showed that the following as the actual build that it wanted to update to:
https://aus5.mozilla.org/update/5/B2G/44.0a1/20151027122943/aries/en-US/dogfood-latest/Boot2Gecko%202.5.0.0-prerelease%20(SDK%2019)/default/default/4066db902a129384e721db0e184d29162c1b74d908ce6ca1c2f72508941a8e52fede9e11861e841c47f92b22d985fc2720ef22236b9d5c2f308630f1ad21c32f/update.xml?force=1

Just posting these as references in case we run into this in the future.

	Jayme Mercado [:JMercado] (Inactive 3/4/2016)
	Comment 8 • 9 years ago

Chris, we aren't seeing this issue anymore so I'm closing as WFM but do you know of anything that might have been causing this server side that occuered today?

	Chris AtLee [:catlee]
	Comment 9 • 9 years ago

The infrastructure servicing aus5.m.o has been migrating this week from PHX1 to SCL3. We had some latency issues which resulted in clients getting 503 errors. I expect this is the cause of this bug.

	Binyamin
	Comment 10 • 9 years ago

Doesn't work for me for http://www.gerloni.net/gp-peak/ images on Peak device 'provided' by https://firefoxos.mozilla.community/device/Geeksphone/Peak