Skip to content

v1.24.1: a fresh cluster's first Longhorn sync creates its namespace

Choose a tag to compare

@thatbagu thatbagu released this 20 Nov 21:11
875d4a1

Fix

A fresh cluster bootstraps by itself. The bootstrap started Longhorn's first sync without the app's sync options or retry, so the sync failed with namespaces "longhorn-system" not found. The failure was final, and every later sync wave waited on Longhorn. The sync now creates the namespace and keeps retrying (#60).

Found by the fully unattended nix run .#reinstall -- <master> --new-cluster on a live 3-node encrypted cluster. With this fix applied by hand, that run finished by itself: all 28 apps came back, every volume and Nextcloud's database were restored, and the data was identical before and after.

Upgrading

Nothing to change in vars.nix. This matters only when a cluster is created; running clusters aren't affected.