c3y1huang
c3y1huang
> Hence, I think this may be caused by a race of condition between the progress update and the device closure. Test results (5/5 PASS): - https://ci.longhorn.io/job/private/job/longhorn-e2e-test/1174/ - https://ci.longhorn.io/job/private/job/longhorn-e2e-test/1175/ -...
> One question: According to your previous report, doesn't the checksum over time although the restore is completed? Is it related to the race condition you mentioned here? Here are...
> Aren't we sure that is a race condition the cause of the mismatching? I think the race condition is causing the mismatches, but this conclusion is based on assumptions...
Summary after discussion with @shuo-wu @derekbit > Why md5sum keeps changing continuously AFTER activation? IIUC, you mean that after each attachment for an activated DR volume, it will show a...
> Hi @c3y1huang , thanks for the explanation. Just a question: do you want to proceed with the PRs with only the race condition fix or do you want to...
Reopen this issue because we also need to update the document on [Root and Privileged Permission - Longhorn Manager](https://github.com/longhorn/website/blob/c4fa470afbf0fc55968020e1417ad40e230ce110/content/docs/1.8.0/deploy/install/_index.md?plain=1#L158-L161) about https://github.com/longhorn/longhorn/pull/9374. cc @derekbit
~Please don't merge the PRs yet. I need to run some tests on them first.~ done cc @longhorn/dev
Test result: - Full: https://ci.longhorn.io/job/private/job/longhorn-tests-regression/5287/ - CSI: https://ci.longhorn.io/job/public/job/v1.4.x/job/v1.4.x-longhorn-tests-sles-amd64/383/ Note that the test_csi_snappshotter cases failed in full regression test due to an incompatibility between the private pipeline's csi-snapshotter (v6.2.1) and Longhorn...
> [#6920 (comment)](https://github.com/longhorn/longhorn/pull/6920#issuecomment-1831808276) @c3y1huang will we update the CSI sidecars as well? https://github.com/longhorn/longhorn/pull/6920#issuecomment-1841870431
> @c3y1huang so, CSI sidecars are only updated to master without backporting to 1.5/1.4, right? We've backported to v1.5 but not 1.4. The reason for backporting to v1.5 was that...