We would like to use the mender configuration add-on in our Mender (3.0) setup.
Unfortunately configuration deployment fails:
2021-09-30 14:16:41 +0000 UTC info: Running Mender client version: 3.1.0 2021-09-30 14:16:41 +0000 UTC info: State transition: update-fetch [Download_Enter] -> update-store [Download_Enter] 2021-09-30 14:16:41 +0000 UTC error: Fetching Artifact headers failed: installer: failed to read Artifact: reader: expecting signed artifact, but no signature file found 2021-09-30 14:16:41 +0000 UTC info: State transition: update-store [Download_Enter] -> update-status-report [none]
Probably the root cause is that our device firmware artifacts are signed and checked via the
*ArtifactVerifyKey* option . Probably the scope of this option is for all types of artifacts including configuration.
As far as my limited knowledge goes are the configuration artifacts created by the mender server but not signed. Is there a work-around?
Thanks in advance.