Closed
Bug 1174308
Opened 9 years ago
Closed 9 years ago
[Flame][OTA] Update sits at 'Uncompressing', shows "Error while downloading the update" after uncompressing, does not finish update
Categories
(Firefox OS Graveyard :: Gaia::Build, defect)
Tracking
(b2g-master affected)
RESOLVED
DUPLICATE
of bug 1085230
Tracking | Status | |
---|---|---|
b2g-master | --- | affected |
People
(Reporter: gaby2300, Unassigned)
Details
(Keywords: regression, smoketest)
I am seeing this issue again today. The last good OTA update was on 28 May, 2015
FF OS 3.0 ans base image v.18D (nightly)
STR
1. Connect to a wifi network.
2. Check for 'Daily Updates' in Settings.
3. Begin the OTA's download.
4. After downloading, notice 'Uncompressing' message.
5. After a few minutes notice it shows "Error while downloading the update"
6. The phone is not updated.
Actual behaviour: the phone is not updated.
Expected behaviour: the phone should be updated.
This bug may or may not be related to Bug 1155704. I filed this new bug by Peter Bylenga's suggestion.
I can confirm the issue.
From logcat:
I/GeckoUpdater( 6962): Progress [ ========================================= ]
I/GeckoUpdater( 6962): Progress [ =============================================== ]
I/GeckoUpdater( 6962): Progress [ ================================================ ]
I/GeckoUpdater( 6962): Progress [ ================================================= ]
I/GeckoUpdater( 6962): Progress [ ================================================== ]
I/GeckoUpdater( 6962): Finished applying update
I/GonkAutoMounter( 6962): Mounted /system partition as read-only
I/Gecko ( 209): *** AUS:SVC readStatusFile - status: failed: 70, path: /data/local/updates/0/update.status
I/Gecko ( 209): UpdatePrompt: Update error, state: failed, errorCode: 70
I/Gecko ( 209): UpdatePrompt: Setting gecko.updateStatus: Install Pending
I/Gecko ( 209): *** AUS:SVC UpdateManager:refreshUpdateStatus - Notifying observers that the update was staged. state: pending, status: failed: 70
system partition size:
/system 354.2M 278.5M 75.7M 4096
There is only 75.7M of free space on /system when OTA has size of 87M.
Found on:
TCT Flame (got from Foxtrot Programme)
B2G version: 3.0.0.0-prerelease master
Platform version: 41.0a1
Build Identifier: 20150612010203
Firmware: v18D
Git commit info: 2015-06-11 18:09:27 9f36b711
Comment 2•9 years ago
|
||
I am seeing this issue occurring in Flame 3.0.
Environmental Variables:
Device: Flame 3.0 (Full Flash)
BuildID: 20150612010203
Gaia: 9f36b711af7597a6a32471c3305cf1e2d6947d39
Gecko: 0093691d3715
Gonk: a4f6f31d1fe213ac935ca8ede7d05e47324101a4
Version: 41.0a1 (3.0)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0
status-b2g-master:
--- → affected
Keywords: regression
There is again problem with it, maybe it would be worth to use SD card in some intelligent way?
1. Check space on /system
2. If there is not enough space on system check space on SD card, i.e. double approximation of unpacked OTA.
3. If there is enough space on SD show message to a user 'Not enough space on the system partition, do you want to proceed with use of SD card storage?' Yes/No
Flags: needinfo?(ffos-product)
Comment 4•9 years ago
|
||
[Blocking Requested - why for this release]:
Functional regression that fails smoketests.
Requesting a window
blocking-b2g: --- → 3.0?
Updated•9 years ago
|
QA Contact: pcheng
Comment 5•9 years ago
|
||
Unable to find a regression window for this bug. It is the build that we're OTA'ing to that has the problem, so no matter what build I'm flashed to, when I OTA it's always going to run into this issue. And we can't control which build we OTA to, so attempting a regression window is a dead end on finding the cause of the issue.
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Keywords: qaurgent,
regressionwindow-wanted
Comment 6•9 years ago
|
||
Naoki, can we get that fix applied on this bug as well?
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker) → needinfo?(nhirata.bugzilla)
Comment 7•9 years ago
|
||
I suspect this bug is of the same cause as bug 1174041. I've already found a regression window for bug 1174041, so we can look at the pushlog and see if the culprit could have also cause this bug.
Comment 8•9 years ago
|
||
I set out to file this bug the other day, but I found bug 1085230, which I believe is about the same thing.
looking at the error 70, I believe that to be the case that this is a dup.
I believe it's a dup at the same time, let's dup this bug and create a new taskcluster bug to add the change in partitions in bug 1085230
Flags: needinfo?(nhirata.bugzilla)
Flags: needinfo?(ffos-product) → needinfo?(ktucker)
Reporter | ||
Comment 10•9 years ago
|
||
I had this issue before. It was solved when a good build was built, in my case I think it had nothing to do with my system space.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Updated•9 years ago
|
blocking-b2g: 3.0? → ---
Flags: needinfo?(ktucker)
You need to log in
before you can comment on or make changes to this bug.
Description
•