Hello, interrupt v2 (yes, needed to save 80% power consumption in idle state) code merged after release rc1 🤨 waiting for rc2. I know that upgrade not supported but for "testers": Replication of volumes (starts but do not replicate and no errors displayed) and Settings UI menu (empty page rendered with console error NULL to firstUpperCase) did not work until I corrected/upgraded some settings `lhs`/`settings.longhorn.io` to keyed (like

value: '{"v1":"true","v2":"true"}'

) -

fast-replica-rebuild-enabled, offline-replica-rebuilding, freeze-filesystem-for-snapshot, snapshot-data-integrity-immediate-check-after-snapshot-creation

. It tested with Harvester v1.6.0 (due to SLmicro5.5 old 5.14 kernel without ublk 🙁).

cc: @salmon-doctor-9726

@loud-potato-42814 v1.10.0-rc2 is just released. You can test it. The recommended Linux kernel is 6.8+

Yes, I noticed this release (and I must wait long for longhornio/longhorn-share-manager to be published). I am limited (and I need it) to Harvester kernel 5.14. V2 engine does not start volume, errors like

E0911 18:36:36.819135       1 panic.go:262] "Observed a panic" panic="runtime error: invalid memory address or nil pointer dereference"

🤔 I will try to find problem ....

hit the

invalid memory address

issue in v1.10.0-rc2?

Yes, but it was transient (un debugable), few restarts of pod after install helps and problem is done. But challenging other persistent problem on baremetal with nvme - https://github.com/longhorn/longhorn/issues/11761 .

E0911 18:36:36.819135       1 panic.go:262] "Observed a panic" panic="runtime error: invalid memory address or nil pointer dereference"

Can you provide the call stack of the panic? We haven't seen the issue in our testing.

Sorry for small context, but have only this small sample in side text file.

Got it. I think you pulled the old and problematic longhorn-manager v1.10.0-rc2 that is not published. We have fixed, rebuilt it and published it. Please make sure pulling images after an offical pre-release. Ref: https://github.com/longhorn/longhorn/issues/11743.

How it is possible ? I used helm to do this work https://github.com/longhorn/charts that pull only published images from dockerhub.

When did you install it?

Exactly 30min after announcement https://rancher-users.slack.com/archives/CC2UQM49Y/p1757571217611879

Got it. The RSS announcement is earlier than the official release of https://github.com/longhorn/longhorn/releases/tag/v1.10.0-rc2. I think we need to fix this.

Wow. I checked SHA and must manually repull ALL images with tag -v1.10.0-rc2 on all nodes manually (different SHA).

Yeah, we will check it next Monday.

V2 has been repaired and should be working again. I don't see anything in the Review/Ready for Testing/Testing sections https://github.com/orgs/longhorn/projects/8/views/29. Is it the right time to publish 1.10.0-rc3? @icy-agency-38675 ?