Closed
Bug 1215733
Opened 9 years ago
Closed 7 years ago
When trying to FOTA the flame device, the device gives a "status text: Update XML file malformed (200)"
Categories
(Firefox OS Graveyard :: Gaia::System, defect)
Firefox OS Graveyard
Gaia::System
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: nhirata, Unassigned)
Details
Attachments
(1 file)
80.54 KB,
text/plain
|
Details |
1. flash v18d_nightly v4 build from the flame update wiki page
2. change the channel to nightly-test
3. reboot the device
4. force an update.
Expected: an update available
Actual: no User feedback, logcat shows :
I/GeckoConsole( 208): AUS:SVC Checker:checkForUpdates - sending request to: https://aus4.mozilla.org/update/3/B2G/41.0a1/20150527010201/flame/en-US/nightly-test/Boot2Gecko%203.0.0.0-prerelease%20(SDK%2019)/default/default/update.xml?force=1
I/GeckoDump( 208): XXX FIXME : Got a mozContentEvent: force-update-check
I/Gecko ( 208): *** AUS:SVC Checker:onError - request.status: 2153389948
I/GeckoConsole( 208): AUS:SVC Checker:onError - request.status: 2153389948
I/Gecko ( 208): *** AUS:SVC getStatusTextFromCode - transfer error: Update XML file malformed (200), default code: 200
I/GeckoConsole( 208): AUS:SVC getStatusTextFromCode - transfer error: Update XML file malformed (200), default code: 200
I/Gecko ( 208): UpdatePrompt: Setting gecko.updateStatus: check-error-2153389948
I/Gecko ( 208): *** AUS:SVC UpdateService:onError - error during background update. error code: -2141577348, status text: Update XML file malformed (200)
I/GeckoConsole( 208): AUS:SVC UpdateService:onError - error during background update. error code: -2141577348, status text: Update XML file malformed (200)
E/Settings( 2384): Content JS ERROR: Error checking for system update: check-error-2153389948
Reporter | ||
Comment 1•9 years ago
|
||
I copied the XML file from the URL ( https://aus4.mozilla.org/update/3/B2G/41.0a1/20150527010201/flame/en-US/nightly-test/Boot2Gecko%203.0.0.0-prerelease%20(SDK%2019)/default/default/update.xml?force=1 )
which shows :
<?xml version="1.0"?>
<updates>
<update type="minor" displayVersion="44.0a1" appVersion="44.0a1" platformVersion="44.0a1" buildID="20151016030225" isOSUpdate="true">
<patch type="complete" URL="http://download.cdn.mozilla.net/pub/mozilla.org/b2g/nightly/2015/10/2015-10-16-03-02-25-mozilla-central-flame-kk/fota-flame-update.mar" hashFunction="sha512" hashValue="6232d0094a95236811818f1953192710542d54ed3a688dd2eeb55417b9487c8f9d974cdbf1cd83b520c3e768c2dd218a9f772b45dd8239ef97c1eed4240bd62c" size="103899988"/>
</update>
</updates>
and then placed that file on a webserver. After doing this, then I changed the app.update.url on the device, rebooted and force checked and the device updated correctly.
I think there's some weird issue on balrog where the hosted file is somehow corrupted? Not certain
Need to follow up with catlee next week.
Flags: needinfo?(catlee)
Reporter | ||
Comment 3•9 years ago
|
||
Catlee asked me to check the url on device using curl
Curl is on the device by default; after an adb shell:
1|shell@flame:/ $ curl https://aus4.mozilla.org/update/3/B2G/41.0a1/2015052701>
.0.0-prerelease%20(SDK%2019)/default/default/update.xml?force=1" <
curl: (60) SSL certificate problem, verify that the CA cert is OK. Details:
error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
More details here: http://curl.haxx.se/docs/sslcerts.html
curl performs SSL certificate verification by default, using a "bundle"
of Certificate Authority (CA) public keys (CA certs). If the default
bundle file isn't adequate, you can specify an alternate file
using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
the bundle, the certificate verification probably failed due to a
problem with the certificate (it might be expired, or the name might
not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
the -k (or --insecure) option.
Reporter | ||
Comment 4•9 years ago
|
||
Turns out to be the wrong error being sent to logcat; the time was fixed and I can download the build just fine.
Moving the bug to client side.
Component: Buildduty → Gaia::System
Product: Release Engineering → Firefox OS
QA Contact: bugspam.Callek
Reporter | ||
Comment 5•9 years ago
|
||
No longer a blocker since I can download buids now. It's an incorrect/inaccurate logcat error.
No longer blocks: 1211965
Reporter | ||
Updated•9 years ago
|
QA Whiteboard: [FOTA Issues]
Comment 6•7 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•