mbed-cloud-client-example no longer works with kvstore FILESYSTEM

[teetak01]

Description of defect

https://github.com/armmbed/mbed-cloud-client-example

Fails to boot-up on K64F when using
"storage.storage_type" : "FILESYSTEM",

kv_init_storage_config() - failed, status -2130771697

Impacts any client using external storage (e.g. dependency to DeviceKey).

Target(s) affected by this defect ?

K64F

Toolchain(s) (name and version) displaying this defect ?

GCC_ARM, ARMC6

What version of Mbed-os are you using (tag or sha) ?

dbf05ce

What version(s) of tools are you using. List all that apply (E.g. mbed-cli)

None applicable

How is this defect reproduced ?

Should be reproducable with the https://github.com/armmbed/mbed-cloud-client-example
using K64F as target as described in tutorial:
https://www.pelion.com/docs/device-management/current/connecting/mbed-os.html

[0xc0170]

cc @ARMmbed/mbed-os-storage

[ciarmcom]

@teetak01 thank you for raising this issue.Please take a look at the following comments:

What version of Mbed OS are you using (tag or sha)?
It would help if you could also specify the versions of any tools you are using?

NOTE: If there are fields which are not applicable then please just add 'n/a' or 'None'.This indicates to us that at least all the fields have been considered.
Please update the issue header with the missing information, the issue will not be mirroredto our internal defect tracking system or investigated until this has been fully resolved.

[ciarmcom]

Thank you for raising this detailed GitHub issue. I am now notifying our internal issue triagers.
Internal Jira reference: https://jira.arm.com/browse/MBOTRIAGE-2658

[teetak01]

With Mbed OS 6.0, the (client) application needs to call now explicitly DeviceKey::generate_root_of_trust().

This is due changes done in #12385 and #12823

Internal ticket https://jira.arm.com/browse/IOTCLT-4179

This will be implemented in future version of Device Management Client.

[0xc0170]

@teetak01 Can we close this issue ? As its being tracked separately.

[teetak01]

Yeah, for reference if someone finds this issue while testing with Mbed OS 6 and external KVstore:

This impacts the usage with external KVstore implementations (FILESYSTEM, TDB_EXTERNAL). The internal-flash only TDB_INTERNAL configuration is fine as that does not have DeviceKey dependencies.