Derek Su
Derek Su
cc @mantissahz (community coordinator)
~~@davidfrickert Could you create a RWX volume and then resize it to see if the issue is always hit?~~ ~~cc @mantissahz Please follow up on the issue and help the...
It is related to https://github.com/longhorn/longhorn/issues/9902. @mantissahz Please help collaborate with @COLDTURNIP to - If possible, add a workaround to mitigate the issue if user is hitting the issue first. -...
@mantissahz @COLDTURNIP Could you help clarify - Will the data be lost after hitting the issue? - Any mitigation to bring the problematic volume back to the normal state after...
> After filesystem check, share manager then [check the encryption status](https://github.com/longhorn/longhorn-share-manager/blob/v1.9.0/pkg/crypto/crypto.go#L118). The device would be considered to be closed since it is is active and is in use rather than...
> I think yes, our original implement should not work. Why doesn't the original impl impact the encrypted volume functionality?
@mantissahz @COLDTURNIP Please update the mitigation in https://github.com/longhorn/longhorn/issues/11120#issue-3147706271. Thanks.
Looks some settings wrong in your deploy manifest. If the issue continued, please provide us the manifest for further investigation.
@COLDTURNIP Please don't set the milestone to a patch version
IMO, this behavior is expected. Modifying `sharemanager.spec.image` cannot immediately propagate to `pod.spec` because the share-manager pod is still serving the running volumes. A feasible solution is to introduce `sharemanager.status.currentImage`, as...