search

PelionIoT / manifest-tool

A tool for creating and parsing update manifests
Apache License 2.0
10 stars 14 forks source link

Update campaign does not start #5

Closed SeppoTakalo closed 3 years ago

SeppoTakalo commented 5 years ago 
$ manifest-tool update device -D 0167cb2b921600000000000100100062 -p ./BUILD/K64F/GCC_ARM-DEBUG/mbed-cloud-client-example_update.bin
[WARNING] 2018-12-20 16:41:33 - manifesttool.update_device - Using mbed-cloud-client-example_update.bin-2018-12-20T16:41:33 as payload name.
[WARNING] 2018-12-20 16:41:33 - manifesttool.update_device - Using mbed-cloud-client-example_update.bin-2018-12-20T16:41:33-manifest as manifest name.
[INFO] 2018-12-20 16:41:38 - manifesttool.update_device - Created new firmware at http://objstore.mbedonprem.com/fw-catalog/mbed-cloud-client-example_update_ee7FOZu.bin
[INFO] 2018-12-20 16:41:38 - manifesttool.update_device - Created temporary manifest file at /var/folders/84/tqqdqp696j73582q658x7pkx0l_yxp/T/tmpqgnu7T/manifest
[INFO] 2018-12-20 16:41:39 - manifesttool.update_device - Created new manifest at http://objstore.mbedonprem.com/fw-catalog/manifest_JshgwXF
[INFO] 2018-12-20 16:41:39 - manifesttool.update_device - Manifest ID: 0167cc10994c0000000000010010036f
[INFO] 2018-12-20 16:41:40 - manifesttool.update_device - Campaign successfully created. Current state: 'draft'
[INFO] 2018-12-20 16:41:40 - manifesttool.update_device - Campaign successfully created. Filter result: {'id': {u'$eq': '0167cb2b921600000000000100100062'}}
[INFO] 2018-12-20 16:41:40 - manifesttool.update_device - Starting the update campign...
[INFO] 2018-12-20 16:41:40 - manifesttool.update_device - Campaign successfully started. Current state: u'scheduled'. Checking updates..
[INFO] 2018-12-20 16:41:41 - manifesttool.update_device - Current state: 'checkedmanifest'
[INFO] 2018-12-20 16:41:42 - manifesttool.update_device - Current state: 'draft'

This hangs forever.

Device does not start update.

SeppoTakalo commented 5 years ago

@teetak01 FYI.

ciarmcom commented 5 years ago

ARM Internal Ref: IOTUC-806

teetak01 commented 5 years ago

Is it possible that in this case the device_id of your development device had changed (thus update is now targetting non-existing device), but the Cloud has not yet realized that the device is gone? With default lifetime of 3600 seconds, it will take a while before the device expires. The tool probably should check the device metadata to see if the device actually is in unreachable state which prevents the campaign from progressing past the draft-state. (IOTUC-779).

You can manually check from the Pelion Device Management portal for more details what the campaign is doing, and also checking the device-specific logs from "Device directory" section and clicking on your Device ID. It has log-section which might reveal any device-reported errors.

moshe-shahar commented 3 years ago

The internal ref has closed long ago.