Chris Chien

I can reproduce in v1.3.1 but not in v1.3.0, In v1.3.0, after reboot the only worker node ( which is worker 2 on my environment), there was only 1 replica...

Thank @mantissahz , After retest this case on v1.3.0, I found I can reproduce error in my local environment, still need time to figure out why last time I can...

Hi @weizhe0422 , If you don't mind, I will take this issue to fix flaky test script, thank you.

After some manual test, I am not sure that this is product issue or script issue In `master-head` I can reproduce by below steps every time 1. Deploy longhorn with...

1. After the I/O error happened, scale down/up deployment let volume detach / attach, the IO error gone and **can** r/w data in deployment pod 2. In longhorn manager log...

Here is the support bundle for reference [longhorn-support-bundle_9893fb8b-4a30-4970-994f-9639d47a6556_2022-10-19T12-28-22Z.zip](https://github.com/longhorn/longhorn/files/9820444/longhorn-support-bundle_9893fb8b-4a30-4970-994f-9639d47a6556_2022-10-19T12-28-22Z.zip)

Here is the instance-manager-r in node-1 1. After manual delete instamce-manager-r on node-1 ``` time="2022-10-19T12:34:26Z" level=info msg="Storing process logs at path: /var/log/instances" -- Wed, Oct 19 2022 8:34:26 pm |...

Hi @PhanLe1010 , As we discussed before, the`Input/output error` can also be reproduced on Longhorn `v1.2.5`, `v1.3.1` and `v.1.3.2` with k3s version `v1.24.7+k3s1`, thank you.

**Verified in longhorn master-head `777bc5` with test [steps](https://github.com/longhorn/longhorn/issues/4239#issuecomment-1272234979) Result Pass** cc @PhanLe1010 , @khushboo-rancher --- ### **Case 1: within a Kubernetes version** - [x] **Test basic recurring snapshot/backup jobs are...

Longhorn chart PR has verified and detail steps [here](https://github.com/longhorn/longhorn/pull/4403#issuecomment-1211907874) Mark related item to checked