Package: slurm-wlm
Version: 24.11.3-2
Severity: normal

Dear Maintainer,


* What led up to the situation?
I did a test upgrade for our slurm controller from latest stable to
current testing.

* What exactly did you do (or not do) that was effective (or
ineffective)?
I did a full upgrade of the machine from stable to testing

* What was the outcome of this action?
The slurmdbd Failed to upgrade the sql database. On startup of the
daemon after the upgrade i get:
fatal: database schema is too old for this version of slurm to upgrade.

* What outcome did you expect instead?
That the daemon would do the migrations.

The stable Version before the upgrade was 22.05.8-4+deb12u2.
After the upgrade i had 24.11.3-2.

The only way to upgrade the database was to compile the 23 version by
hand, run only the database daemon (which did the migrations of the
database to 23) and than start the 24 Version.

Maybe that should be added to the release notes for Trixie or is there
another way to enable migrations between the versions?

Regards,
Jan


-- System Information:
Debian Release: 13.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.12.27-amd64 (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US.UTF-8
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)