Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Feature: Upgrade Longhorn to 1.7.2 or higher #1707

Closed
2 tasks
JKBGIT1 opened this issue Mar 31, 2025 · 0 comments · Fixed by #1709
Closed
2 tasks

Feature: Upgrade Longhorn to 1.7.2 or higher #1707

JKBGIT1 opened this issue Mar 31, 2025 · 0 comments · Fixed by #1709
Labels
feature New feature

Comments

@JKBGIT1
Copy link
Contributor

JKBGIT1 commented Mar 31, 2025

Motivation

A critical bug fix was fixed in Longhorn 1.7.2 and later. The bug resolves issues with RecurringJobs, which handles scheduled backups. More details can be found in the related issue:
longhorn/longhorn#7814
longhorn/longhorn#7814 (comment)

Description

Longhorn's scheduled backup process gets stuck when backing up a specific volume, potentially lasting indefinitely. As a result:

  • No backup is created for the affected volume.
  • Subsequent backups for other volumes remain blocked.
  • Longhorn never initiates another round of scheduled backups because the stuck process never completes.

Exit criteria

  • Verify whether Longhorn can be upgraded without data loss or other issues.
  • Upgrade Longhorn to 1.7.2 or higher
@JKBGIT1 JKBGIT1 added the feature New feature label Mar 31, 2025
@Despire Despire mentioned this issue Apr 1, 2025
Merged
github-merge-queue bot pushed a commit that referenced this issue Apr 1, 2025
@Despire
chore: update dependencies & longhorn to 1.8.1 (#1709)
9b603b8 
General dependencies update across the repository.

Updates longhorn to 1.8.1. Closes
#1707
This was tested by creating a deployment with pvc with loghorn 1.7.0
(the current version)
Upgrade to longhorn 1.8.1, all pods were deployed successfully, perform
additional operation on the cluster without issues.
  The hash of the replicas were the same after the upgrade.
Further longhorn also specifies in the release that 1.8.x is backwards
compatible with 1.7.x
https://github.com/longhorn/longhorn/releases/tag/v1.8.1
  
For volumes created with the old instance one can follow:
https://longhorn.io/kb/troubleshooting-some-old-instance-manager-pods-are-still-running-after-upgrade/
It's possible to set via the Longhorn UI `Settings > Concurrent
Automatic Engine Upgrade Per Node Limit` to a value higher than 0 to
upgrade old volumes to the newly deployed manager
  
Old engine-image pods will be terminated after ~60 minutes of not being
used (after all volumes are upgraded to the newest longhorn version)
  
  Updates go to 1.24.
  
  Updates go dependencies

---------

Co-authored-by: CI/CD pipeline <CI/[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature New feature
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

chore: update dependencies & longhorn to 1.8.1 berops/claudie
1 participant
@JKBGIT1