Uploaded image for project: 'Mender'
  1. Mender
  2. MEN-5181

Option to force update even if already installed



    • Type: Epic
    • Status: To Do
    • Priority: (None)
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None


      When Mender sees that the Artifact name installed is the same as the one to be deployed, it will Skip the update. This is very good for most scenarios (avoid downtime, risk of issues).

      However there are some "corner cases" discovered where this inhibits use or becomes very inconvenient:

      • Device "restore" when diagnosing. You get a support request and need to make some ad-hoc changes to a in-field device. Now you figured out what's wrong and would like restore the version that was already running on the device. But you can't, because Mender thinks that you already are running the same version even though it's been manually modified. This usually applies only to single devices.
      • During testing / PoC. You're deploying a full image update, then "hacking" a bit on it, creating and Artifact and deploy it again. Unless you remember to change the version it won't be deployed. This usually applies only to single devices.
      • More advanced / custom cases where you have multi-partition setup with OS and apps and the partitions need to be in sync. See ZD for an example.

      Acceptance criteria

      • During deployment creation, it is possible to enable "Force update" and in the UI it explains that it will install it even if Mender detects this update is already installed
      • There is an option to force update in standalone mode (mender -install)
      • In all cases, the default is force = disabled
      • This feature is available in all plans and editions, including open source


          Issue Links



              Unassigned Unassigned
              a10003 Eystein Maloy Stenberg
              0 Vote for this issue
              4 Start watching this issue