Mender on Azure: Can not up/download releases after upgrades

General Discussions
1

After updating a Mender 3.6 instance on Azure to 3.7 and then to 4.0, it’s not possible to upload or download releases. We noticed that some releases were missing and that we could neither upload new releases nor download any of the remaining ones.

Rolling back to version

  • 3.7 resolved the upload issue, but some releases were still missing and we could still not download any of them.
  • 3.6 restored the missing releases, and uploading and downloading became possible again.

We performed a similar upgrade on a different Mender deployment which worked fine. The difference is, that it used S3 instead of Azure. We assume these problems are Azure-related.

Has anyone had similar problems when upgrading on Azure?

2

Hello @dbasner from 3.x to 4.x there has been a helm chart major upgrade with some breaking changes; in particular for the artifacts storage, the Storage Proxy feature is enabled by default, see: mender-helm/UPGRADE_from_v5_to_v6.md at master · mendersoftware/mender-helm · GitHub

If you want to restore the 3.x configuration with the Mender Server v4.0, you should explicitly disable the Storage Proxy:

api_gateway:
  storage_proxy:
    enabled: false

deployments:
  customEnvs: []

If that’s not the case, you could share more details of your issue, to better understand what’s happening.