Martin Shuman [:Marty] Reporter
	Description • 9 years ago

Description:
Currently, build 20150608110222 is available on the Aries Dogfood OTA channel.  The actual latest build is 20150608200123.

Repro Steps:
1) Update a Aries to 20150608110222
2) Connect to WiFi or Data
3) Check for Updates

Actual:
Update is not found, because the device is already on the build found in the channel.

Expected:
A System Update for build 20150608200123 is found.

Environmental Variables:
Device: Aries 3.0
Build ID: 20150608110222
Gaia: 592b6cf0ffc7f487b0c52a8a74ce8ac389a593c6
Gecko: 4700d1cdf489
Gonk: 3af1ede0d0956cfbf9c549df7cd9a6807a9efdf2
Version: 41.0a1 (3.0)
Firmware Version: D5803_23.1.A.1.28_NCB.ftf
User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0

Repro frequency: 5/5

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

Spoke with Marty and debugged at the same time:
1) checked the rule, the rule is currently set to:
 B2G : dogfood
Mapping: B2G-mozilla-central-nightly-latest
2) checked the releases:
aries-userdebug":
"buildID": "20150601233616",

"aries": { buildID": "20150608110222"
3) checked the rules again and saw that it was pointing to aries not aries-userdebug.  Changed the rules for dogfood to point to aries-userdebug.

Should be fixed now.

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

Reopened.  I looked at it too quickly.  It might be partially due to the tree closure but I need to investigate some more.

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

https://tools.taskcluster.net/task-inspector/#jvOyU24sQ--PDsSGOOj5BA/ is the build I see at this current time.
hg rev: e10e2e8d8bf22ee704d8b6f748a025fed5dd6ac2


Looking at treeherder, that's the last green aries-dogfood.  The others are red.

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

Weird.  flashing that build does give a 20150608200123.  

https://tools.taskcluster.net/index/artifacts/#gecko.v1.mozilla-central.revision.linux.010ecb3b3b25616052550722940bbf9faba1cf89/gecko.v1.mozilla-central.revision.linux.010ecb3b3b25616052550722940bbf9faba1cf89

Does show as the second revision in the list.

Which means that the releases isn't getting updated... it's not taskcluster.  It's how balrog is getting it's info...

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

Oh interesting.  looking at the task for the aries from balrog : 
https://tools.taskcluster.net/task-inspector/#rU92F9XVRCCIqHuZ4CkmKg/ 
it's pointing to the dogfood not the user build.

Switched the balrog rules back.  So balrog needs to somehow get the proper versioning.
Also to note, we still don't have the shiny new ui... might need to file a separate bug.

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

Switching to Taskcluster to Balrog release info issue.  Asking wander to take further investigation why this is broken.

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

Looks like something changed.  Looking at the aus releases again, it's now showing aries as using the aries-ota and the aries-userdebug as the dogfood build.

dogfood shows : build 20150610170534 is being used... which matches aries-debug.
OTAing showing build 2015610165040 is being used... which matches aries

I changed the rules from aries to aries-debug again.
In order to get the update for dogfood, the %PRODUCT_DEVICE% needs to be changed on the client side to aries-debug:

ie : https://aus4.mozilla.org/update/3/B2G/41.0a1/20150608200123/aries/en-US/dogfood/Boot2Gecko%203.0.0.0-prerelease%20(SDK%2019)/default/default/update.xml?force=1

is what it looks for as default.  The Update URL needs to change so that the %PRODUCT_DEVICE% is using aries-userdebug like so:

https://aus4.mozilla.org/update/3/B2G/41.0a1/20150608200123/aries-userdebug/en-US/dogfood/Boot2Gecko%203.0.0.0-prerelease%20(SDK%2019)/default/default/update.xml?force=1

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

Talking to wcosta, looks like he made a patch to fix this and I should change aries-dogfood back to aries.  see Bug 1173328: Dogfood builds always have "aries" as the platform name.

It should be fixed once https://hg.mozilla.org/integration/b2g-inbound/rev/22e7e595584a lands on central.  changed aries-dogfood back to aries.

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

QAWANTED: Should be fixed now.  Please verify.

	Oliver Nelson [:oliverthor]
	Comment 10 • 9 years ago

OTA path is still not pointing to the latest TaskCluster

OTA from buildpath: 20150609205239
OTA brings device to buildID:20150611132111

Full Flash build from same date ['latest' taskcluster]: 20150611131651


Device: Aries 3.0
BuildID: 20150611131651
Gaia: 68269e7b6510930eb2f644f69d27d456c1bdec75
Gecko: 9ebd530c5843
Gonk: 75c7e6ca80d0c7a53f346ecfcde2343be95808c9
Version: 41.0a1 (3.0) 
Firmware Version: D5803_23.1.A.1.28_NCB.ftf
User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0

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

Can you check again?  I see the Build Identifier in the settings state the right build, the build number which is the gonk layer will give eng.worker.20150609.231140 for this build:

https://tools.taskcluster.net/index/artifacts/#gecko.v1.mozilla-central.revision.linux.8be8deb10e4f4b3705aa3ffd62cd38f0fae209f3.aries-dogfood/gecko.v1.mozilla-central.revision.linux.8be8deb10e4f4b3705aa3ffd62cd38f0fae209f3.aries-dogfood.debug

	Oliver Nelson [:oliverthor]
	Comment 12 • 9 years ago

Comparing the Build Number of both of the builds I mentioned in comment #10 show identical results:
Full: 20150611131651
Build Number: eng.worker.20150611.130230

OTA: 20150611132111
Build Number: eng.worker.20150611.130230


They also compare identically with Gaia and Gecko Hashes:
Device: Aries 3.0
BuildID: 20150611131651 && 20150611132111
Gaia: 68269e7b6510930eb2f644f69d27d456c1bdec75
Gecko: 9ebd530c5843
Gonk: 75c7e6ca80d0c7a53f346ecfcde2343be95808c9
Version: 41.0a1 (3.0) 
Firmware Version: D5803_23.1.A.1.28_NCB.ftf
User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0

So regardless of BuildIdentifier, they appear to be the same build.
Not sure what you wanted me to do with your linked build (06/09), but ni? me again if there's anything further you'd like me to try.

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

Spoke to oliver via irc and he confirmed it was good:

oliverthor: The build I chose OTA'd to 20150611132111 just fine, I picked a build we had saved with an earlier build date
[1:58pm] nhirata_: ok so it's ok?
[2:00pm] oliverthor: Yeah, the build number matched from OTA and Full flash for 06/11
[2:00pm] oliverthor: both: eng.worker.20150611.130230

	Pete Moore [:pmoore][:pete]
	Comment 14 • 9 years ago

Resetting Version and Target Milestone that accidentally got changed...