Known issue in mender-client versions 3.1/3.2 - update failing

Hi all,
there is an identified issue with the recent versions of the mender-client.
This blog post describes the issue and provides a workaround.
The Mender team apologizes for the inconveniences and stress this might have caused.

Issue summary

Clients affected

  • 3.1.0
  • 3.1.1
  • 3.2.0
  • 3.2.1


A freshly factory flashed device doesn’t have the mender DB initialized.
When deploying a full system update on that kind of device, the deployment will fail.

One of the following will be printed in the logs:

Attempting to upgrade to currently installed artifact name, not performing upgrade 
Device provided conflicting request data.


Create an empty file and upload it as a single-file artifact.
Deploy that artifact to the device.
This will initialize the mender DB.
Once the file was deployed, the previously failing deployments will from now on all work.




Step by step video on how to deploy the workaround.


I’m so glad that I was redirected by Support to this topic as this exact issue started to show this week. The week where we started delivering “freshly factory flashed” devices to our customers which could not be updated due to this issue. The workaround is at least keeping us going forward, but very keen on seeing an updated client release!


PS One suggestion might be to change the title of this topic to include the “symptom” of a failing update instead of the current generic title

1 Like