Closed
Bug 1161579
Opened 9 years ago
Closed 9 years ago
[OTA] Unable to find System Update
Categories
(Toolkit :: Application Update, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1155704
blocking-b2g | 2.5+ |
Tracking | Status | |
---|---|---|
b2g-master | --- | verified |
People
(Reporter: onelson, Assigned: aus)
References
Details
(Keywords: regression, smoketest, Whiteboard: [3.0-Daily-Testing][systemsfe])
Attachments
(1 file)
108.90 KB,
text/plain
|
Details |
Description: When a user attempts to perform an OTA from the build 20150504010202, they will observe that no update will be found after numerous attempts to 'Search for Updates' in settings. If the user were to attempt to perform the same update from an earlier nightly, 20150501010203 was tested, they will obesrve that the update will be found AND they will be brought to the latest nightly, 20150505010204 * 20150504010202 --> No OTA found * 20150501010203 --> 20150505010204 Repro Steps: 1) Update a Flame to 20150504010202 2) Open Settings 3) Enable Wi-Fi 4) Navigate to Device Information 5) Search for Updates Actual: Unable to find OTA Expected: OTA is found and available for user to update Environmental Variables: Device: Flame 3.0 Build ID: 20150504010202 Gaia: e18cce173840d6ff07fb6f1f0e0ffb58b99aab3e Gecko: dc5f85980a82 Gonk: a9f3f8fb8b0844724de32426b7bcc4e6dc4fa2ed Version: 40.0a1 (3.0) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:40.0) Gecko/40.0 Firefox/40.0 Repro frequency: from 20150504010202: 8/8, cannot find an update from 20150501010203: 0/2, finds update
Reporter | ||
Updated•9 years ago
|
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
Reporter | ||
Comment 1•9 years ago
|
||
Attached logcat from performing 'Check Now' for daily updates on the affected build listed above, 20150504010202
Reporter | ||
Comment 2•9 years ago
|
||
Issue does not repro for 2.2 on flame devices: Results: OTA is found and available for user to update Device: Flame 2.2 BuildID: 20150504002502 Gaia: 8d14361337e608c8cdf165ea5034db5eda23b618 Gecko: cb7cb6597c91 Gonk: a9f3f8fb8b0844724de32426b7bcc4e6dc4fa2ed Version: 37.0 (2.2) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0
Keywords: regression
Comment 3•9 years ago
|
||
[Blocking Requested - why for this release]: Sanity blocker. Requesting a window.
blocking-b2g: --- → 3.0?
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
Keywords: qaurgent,
regressionwindow-wanted
Whiteboard: [3.0-Daily-Testing] → [3.0-Daily-Testing][systemsfe]
Updated•9 years ago
|
QA Contact: ychung
Comment 4•9 years ago
|
||
I am unable to go further from the central regressions window. According to the pushlog, bug 1154947 might be the cause. Here's what I found initially: Mozilla-Central Regression Window: Last Working Environmental Variables: Device: Flame 3.0 BuildID: 20150430133001 Gaia: 759a1f935a6a81c32ad66e39a6353b334dfa4f91 Gecko: 7723b15ea695 Version: 40.0a1 (3.0) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:40.0) Gecko/40.0 Firefox/40.0 First Broken Environmental Variables: Device: Flame 3.0 BuildID: 20150501074537 Gaia: 8e64346ce8197b50b815a294278797bc144aa3e6 Gecko: 60b269fed8cf Version: 40.0a1 (3.0) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:40.0) Gecko/40.0 Firefox/40.0 Last Working Gaia First Broken Gecko: Issue DOES reproduce Gaia: 759a1f935a6a81c32ad66e39a6353b334dfa4f91 Gecko: 60b269fed8cf First Broken Gaia Last Working Gecko: Issue does NOT reproduce Gaia: 8e64346ce8197b50b815a294278797bc144aa3e6 Gecko: 7723b15ea695 http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=7723b15ea695&tochange=60b269fed8cf
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Keywords: regressionwindow-wanted
QA Contact: ychung
Comment 5•9 years ago
|
||
Wander, can you take a look at this please? This might have been caused by the landing for bug 1154947. We are only guessing here since the pushlog is quite large but that bug seems like the most likely suspect. We will need this backed out if this is the case since it is causing a sanity blocker.
Blocks: 1154947
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker) → needinfo?(wcosta)
Catlee, James, the move to taskcluster is breaking OTA, we do need OTA for aries. Could either of you have someone take a look at this please in how we can fix it? It's breaking smoke tests so it's a bit urgent.
Flags: needinfo?(jlal)
Flags: needinfo?(catlee)
Comment 7•9 years ago
|
||
Hey Naoiki, The timing is a bit awkward wcosta is totally unavailable right now so I have asked Aus to step in with the update bits... Please coordinate with him for Aries for the time being.
Flags: needinfo?(wcosta)
Flags: needinfo?(jlal)
Flags: needinfo?(catlee)
I am aware that the timing is awkward. It's rather unfortunate. Thanks, Aus for stepping in! Really appreciate it.
Flags: needinfo?(aus)
To note, we also need OTA to work on Flame devices. I should also mention that. It's causing a smoke test blocker.
Updated•9 years ago
|
blocking-b2g: 3.0? → 3.0+
Comment 10•9 years ago
|
||
(In reply to KTucker [:KTucker] from comment #5) > Wander, can you take a look at this please? This might have been caused by > the landing for bug 1154947. We are only guessing here since the pushlog is > quite large but that bug seems like the most likely suspect. We will need > this backed out if this is the case since it is causing a sanity blocker. Ok, I broke OTA with this commit http://hg.mozilla.org/mozilla-central/rev/86d907839999 This was created so non-user variant builds would have their own updates. backing out this will not break aries updates, but userdebug variant will receive user OTA updates. How this is handled for flame?
Comment 11•9 years ago
|
||
(In reply to Wander Lairson Costa [:wcosta] from comment #10) > (In reply to KTucker [:KTucker] from comment #5) > > Wander, can you take a look at this please? This might have been caused by > > the landing for bug 1154947. We are only guessing here since the pushlog is > > quite large but that bug seems like the most likely suspect. We will need > > this backed out if this is the case since it is causing a sanity blocker. > > Ok, I broke OTA with this commit > http://hg.mozilla.org/mozilla-central/rev/86d907839999 > This was created so non-user variant builds would have their own updates. > backing out this will not break aries updates, but userdebug variant will > receive user OTA updates. How this is handled for flame? wander, can you please back this out till you have a proper forward fix?
Flags: needinfo?(wcosta)
Assignee | ||
Comment 12•9 years ago
|
||
Backed out until we figure out the right way to do this. :) https://hg.mozilla.org/mozilla-central/rev/b90ebba4306d
Flags: needinfo?(wcosta)
Flags: needinfo?(aus)
Assignee | ||
Comment 13•9 years ago
|
||
Taking care of this on behalf of wcosta, please contact me and me only for this issue. Thanks!
Assignee: nobody → aus
Assignee | ||
Comment 14•9 years ago
|
||
Looks like we have a few more dependencies to satisfy before we can re-land the original work that caused this problem. IRC convo snippet -- 3:04:40 PM wcosta: hrm, I have some flame nightly work for TC, but it does not have eng and userdebug builds 3:14:21 PM auswerk: gotcha 3:14:49 PM auswerk: do you have a partial patch for that specifically that you could just hand over to me? I'm happy to finish the work on this with naoki 3:16:33 PM wcosta: I landed it on m-c http://hg.mozilla.org/mozilla-central/file/5593ac626826/testing/taskcluster/tasks/builds/b2g_flame_kk_nightly.yml 3:17:06 PM wcosta: but it is not scheduled yet because we need to land bug 1156816 3:17:55 PM wcosta: bug 1156816 is ready to land, but I prefer to push it when I am back, just in case I break more things 3:20:14 PM auswerk: cool, well, we can just re-land everything at that time then 3:20:23 PM auswerk: QA can continue working with Flame (and others) So basically, we'll be able to wrap up all the things next week. In the meantime, the original issue is resolved. We should have a build to confirm this shortly.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Updated•9 years ago
|
Comment 15•9 years ago
|
||
This issue is Verified Fixed on Flame 3.0. I was able to successfully discover and apply an OTA update from build 20150507010205 to build 20150507064907. Environmental Variables: Device: Flame 3.0 Build ID: 20150507010205 Gaia: 426fe6450ab8da92bb473fef12ccb39c6c920dd0 Gecko: 617dbce26726 Gonk: a9f3f8fb8b0844724de32426b7bcc4e6dc4fa2ed Version: 40.0a1 (3.0) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:40.0) Gecko/40.0 Firefox/40.0
Updated•9 years ago
|
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(pbylenga)
Comment 16•9 years ago
|
||
Per Comment 15, set "status-b2g-v3.0" as "verified".
Comment 17•9 years ago
|
||
If I'm already on the affected version, do I need to re-flash my flame?
Comment 18•9 years ago
|
||
(In reply to Kan-Ru Chen [:kanru] from comment #17) > If I'm already on the affected version, do I need to re-flash my flame? Yes, you do.
Updated•9 years ago
|
status-b2g-v2.5:
--- → verified
Target Milestone: --- → 2.2 S12 (15may)
Updated•9 years ago
|
status-b2g-v2.5:
verified → ---
Comment 19•9 years ago
|
||
Moving the bug to the component where the regression came from.
Component: Gaia::System → Application Update
Product: Firefox OS → Toolkit
Target Milestone: 2.2 S12 (15may) → ---
Comment 20•9 years ago
|
||
No patch to fix this and since this is likely the same as bug 1155704 duping
Status: VERIFIED → RESOLVED
Closed: 9 years ago → 9 years ago
Resolution: FIXED → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•