PhanLe1010
The bash command would be like `git clone https://github.com/longhorn/longhorn.git && cd longhorn && helm install longhorn ./chart --namespace longhorn-system --create-namespace` Another alternative is `kubectl apply -f https://raw.githubusercontent.com/longhorn/longhorn/master/deploy/longhorn.yaml`
**Workaround:** Since the volume has only 1 replica in this case, we can: 1. Scale down the workload. Longhorn volume will be detached 2. Wait for Longhorn volume to be...
>To prevent from the mistaken deletion of the engineimage, we can count the number of replicas and engines using the image rather than the number of volumes. Sounds good to...
> If a volume with multiple replica and some replicas' volume.meta have illegal values, we can consider deleting these problematic replicas and avoid the failure. I agree with this point
@Mafalda22 Do you still have issue here? @mantissahz Could you please put the slack link here? Thank you
Thanks @Arsenikki for reporting. We will investigate this issue. In the mean time, if you see the problem again, can you send us a support bundle to `[email protected]`
Adding @joshimoo as assignee as we are co-working on this ticket
It could take up to 6 or 7 minutes for Kubernetes to retry creating the volumeattachment object. How long did the node go down?
@diamonwiggins I don't seem to figure out why the VA is deleted and never been created automatically as you mentioned earlier that the VA removal feature was removed since Longhorn...