Jack Lin

It seems there is no way to customize the helm command error message - https://github.com/helm/helm/issues/12017 - https://github.com/helm/helm/issues/12002 During uninstallation, Longhorn creates a `longhorn-uninstall` pod to clean up the resources. If...

Hi @mantissahz , I have reviewed the PR, PTAL, thanks!

BTW, do we have upgrade plan for the new backup CRD changes I think we need to modify the backup CRDs when user upgrades from previous version to this version...

I think if we can make sure `system backup` and `csi` backup can support specifying backupTarget instead of using default Then we can remove the default concept and the handling...

Can you help to generate the support bundle when the issue happens again? Thanks

Yes, when it is read-only, sometimes it can't be remount due to the device becomes write-protected. We are now trying another approach to see if we can prevent it from...

Waiting for https://github.com/longhorn/longhorn/issues/8757 to be finished So we can also check the remaining backing image on the evicted node/disk

Close as we already can use `storageAllocated` to see if there are remaining resources on the node or disk. ref: https://github.com/longhorn/longhorn/issues/10522

## Test Steps - Create a sparse file `test` (`$ truncate -s 512M backing.img`) - Create a BackingImage `test` with this sparse file - Create a BackingImage with a ubuntu...

@innobead No we don't have **backup failover**, once there is a block failed to upload, it should failed with the error message Another `e2e-test-volume-1` doesn't work either From the log...