We have a test machine booted with release version 6 (which was installed manually with a rootfs-image local file with
mender install version6.mender).
Our cloud server for release version 1 has these artifacts uploaded:
- rootfs-image for 1
- mender-binary-delta from 0 to 1
- mender-binary-delta from 2 to 1
The differentials are produced by
If I were to start a deployment to that test machine for release 1, one would expect the server would choose rootfs-image for 1. In reality server sends mender-binary-delta from 2 to 1 which of course fails (“rootfs_image_checksum” not satisfied by currently installed artifact ([hash_of_2] != [hash_of_6]).
Deleting mender-binary-delta from 2 to 1 and retrying, the server picks the other differential and fails again.
Deleting every other differential, the server finally chooses rootfs-image for 1 and succeeds.
Uploading another differential from 6 to 1 (while keeping the rootfs-image for 1) chooses correctly that differential and installs it fine.
Can something be wrong on the test machine or is it a bug on the server?