This message was deleted.
# longhorn-storage
a
This message was deleted.
l
cc: @salmon-doctor-9726
i
@loud-potato-42814 v1.10.0-rc2 is just released. You can test it. The recommended Linux kernel is 6.8+
l
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 ....
πŸ‘€ 1
i
hit the
invalid memory address
issue in v1.10.0-rc2?
l
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 .
i
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.
cc @billowy-painting-56466
cc @@creamy-keyboard-76843
l
Sorry for small context, but have only this small sample in side text file.
It was different issue, because of transient nature, I did not reported it.
i
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.
l
How it is possible ? I used helm to do this work https://github.com/longhorn/charts that pull only published images from dockerhub.
i
When did you install it?
l
i
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.
πŸ˜„ 1
We found the issue after RSS announcement and before the official release. πŸ˜…
l
Wow. I checked SHA and must manually repull ALL images with tag -v1.10.0-rc2 on all nodes manually (different SHA).
πŸ‘ 1
Restarted. Problem https://github.com/longhorn/longhorn/issues/11761 still pending.
i
Yeah, we will check it next Monday.
πŸ‘ 1
l
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 ?