Here we cover how to upgrade to latest Longhorn from all previous releases.
There are normally two steps in the upgrade process: first upgrade Longhorn manager to the latest version, then manually upgrade the Longhorn engine to the latest version using the latest Longhorn manager.
After Longhorn Manager is upgraded, Longhorn Engine also needs to be upgraded using the Longhorn UI.
Since Longhorn v1.1.1, we provide an option to help you automatically upgrade engines
Note: There is a bug in the instance manager image
v1_20201216shipped in Longhorn v1.1.0 and v1.1.1 which can lead to a deadlock in a big cluster with hundreds of volumes. See more details here. Longhorn v1.1.2 is shipped with a new instance manager image
v1_20210621which fixed the deadlock but engine/replica processes of volumes don’t migrate from the old instance manager to the new instance manager until the next time the volumes are detached/attached. Longhorn does it because we don’t want to interrupt the data plane of the volumes.
If you hit the deadlock in the old instance manager, please follow the recovering steps here
If you have any issues, please report it at https://github.com/longhorn/longhorn/issues and include your backup yaml files as well as manager logs.
© 2019-2023 Longhorn Authors | Documentation Distributed under CC-BY-4.0
© 2023 The Linux Foundation. All rights reserved. The Linux Foundation has registered trademarks and uses trademarks. For a list of trademarks of The Linux Foundation, please see our Trademark Usage page.