Closed
Bug 904744
Opened 12 years ago
Closed 12 years ago
[B2G] [Leo] [Notification] Device on nightly channel receives system update despite being on latest build
Categories
(Firefox OS Graveyard :: Gaia::System, defect)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
People
(Reporter: ckreinbring, Unassigned)
Details
Attachments
(1 file)
|
189.74 KB,
text/plain
|
Details |
Description:
After flashing to today's build, there will be a build update available to download. However this update will set the device to a previous day's build even though the device is on the Nightly update channel.
Repro Steps:
1) Update Leo to Build ID: 20130812041203
2) Wait for the build update notification to appear.
3) Download and install the update.
4) When the device restarts, check the build ID.
Actual:
The device build is "updated" to a previous day's version.
Expected:
Build update does not appear since the user is already on the latest version.
Environmental Variables
Occurs on Leo 1.1 commercial RIL
Build ID: 20130813041202
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/36bbc5943448
Gaia: df57dcec720493bedff4601499d78c147ad7d253
Platform Version: 18.1
RIL Version: 01.01.00.019.190
Notes:
Repro frequency: 1 out of 6 devices
See attached logcat logs
Updated to
Build ID: 20130812041203
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/36bbc5943448
Gaia: c60e3507d9df160e006d2e25967d26df2dc543cb
Platform Version: 18.1
RIL Version: 01.01.00.019.190
Comment 2•12 years ago
|
||
This sounds like the server has the wrong version of firmware.
Unfortunately, the log doesn't contain the update, so I can't check which URL was being used.
Adding needinfo on the reporter to provide the log of the update itself (so grab the log after the update has finished downloading).
Flags: needinfo?(dhylands) → needinfo?(ckreinbring)
Comment 3•12 years ago
|
||
So, it isn't clear from the STR which of the 2 builds is the starting build.
2 builds are mentioned: 20130813041202 and 20130812041203
The STR says to update to the earlier of these (20130812041203) and then says it was updated to the same one (not the previous days).
So I figured I'd ask for clarification.
| Reporter | ||
Comment 4•12 years ago
|
||
Sorry, the starting build was supposed to be 20130813041202.
| Reporter | ||
Comment 5•12 years ago
|
||
I attempted to repro again using multiple Leo devices, and using both today's and yesterday's build. I was unable to repro the issue.
We suspect that there was a bad update URL yesterday, but it goes to the proper URL now. Resolving as Worksforme for now.
Build ID: 20130814041202
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/15813d776a69
Gaia: dd3959fa74e356a528daa76ffee14c2c728a4b56
Platform Version: 18.1
RIL Version: 01.01.00.019.190
Build ID: 20130813041202
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/36bbc5943448
Gaia: df57dcec720493bedff4601499d78c147ad7d253
Platform Version: 18.1
RIL Version: 01.01.00.019.190
Status: NEW → RESOLVED
Closed: 12 years ago
Flags: needinfo?(ckreinbring)
Resolution: --- → WORKSFORME
Updated•12 years ago
|
blocking-b2g: leo? → ---
| Reporter | ||
Comment 6•12 years ago
|
||
Verifying as Worksforme due to being unable to repro on Leo 1.1 commercial RIL. The system update notification has still not appeared.
Environmental Variables
Build ID: 20130904041204
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/307824edadd7
Gaia: d0a415bbf23e5d01c2b287d9fca708e167cfe70d
Platform Version: 18.1
RIL Version: 01.01.00.019.212
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•