PhanLe1010
Images PR: https://github.com/rancher/image-mirror/pull/294
Yeah, please check if you have set the node selector and taint toleration as mentioned in the doc provided by @innobead
With your proposal, we can also avoid some misleading error messages when the engine panic because it cannot connect to the its replicas
@konstantin-921 It is ok to upgrade directly to `100.1.2+up1.2.4` in the new UI. We have verified this upgrade path Please don't use Helm here, it will conflict
@konstantin-921 What do you set it to? is it `disable`?
Thank you! This might be related to the weekhook in Longhorn v1.3.0 version. I am investigating it. Please do report if you hit any other issue
Hello there! Sorry for the late response. It looks like you had the problem mentioned in [this knowledge base article](https://longhorn.io/kb/troubleshooting-volume-filesystem-corruption/#solution). The article also has instruction how to recover. Please let...
> n mean time can you give us any diagnostic about why this happened and what happened? it was an in use volume, and was the only corrupted volume in...
If there was no issue with the node where the workload pod (the pod that is using a Longhorn volume) running on AND there is only one failed replica, this...
> So this occurred because one replica corrupted, not all 3 I couldn't find the evidence in the support bundle to support this statement. In the support bundle, there is...