Derek Su
Derek Su
Hello @srgvg, I found the `pvc-31971a3f-cd85-4dc5-b103-86c3dc64cfab` is deleted, so the volume CR information is missing. ``` involvedobject: kind: Volume namespace: longhorn-system name: pvc-31971a3f-cd85-4dc5-b103-86c3dc64cfab uid: 0d4de8a1-3815-4f76-b4ca-4e7d45f5ce05 apiversion: longhorn.io/v1beta1 resourceversion: "321406219" fieldpath:...
> Yes, I had to fix the issue, and the request on Slack for the support bundle came later I guess. I'll wait for a similar case to happen, and...
@andrewheberle Can you check the longhorn-managers' log and provide us the error/warning messages?
From the local-path-provisioner tests' results, the SSDs specs in the AMD and ARM machines should be different.
> After creating a snapshot, Longhorn volume can calculate the checksum then store it in the metafile along with the modification time. Can the checksume be stored in the `snapshot.spec`?
### Benchmark #### x86_64 | -- | -- | | ---- | ---- | | Kubernetes | v1.24.4+rke2r1 (3 worker nodes) | | Longhorn | master-head with snapshot checksum feature...
e2e https://ci.longhorn.io/job/private/job/longhorn-tests-regression/2485/console
> > Update: > > > > * Longhorn v1.1.2 + RKE1 (v1.20.10): working fine > > * Longhorn v1.1.2 + RKE2 (v1.21.4+rke2r2): Failed > > ``` > > MountVolume.WaitForAttach...
Will be handled in https://github.com/longhorn/longhorn/issues/5189
Yeah, the implementation is for resilience and the root cause is not identified.