Closed KyleSponz closed 2 years ago
@KyleSponz Could you please add more details, thanks.
The Harvester version
The cluster scale, single node or multi node, node number.
The node resource, CPU cores, memory, storage
Could you also attach a few pictures or logs about that status.
And kubectl get pvc -A -o YAML
, kubectl get volume -A -o YAML
, kubectl get vm -A -o YAML
...
It is possble that the VM's claimed storage size is big than the usable space, that causes the PVC is unable to be attached.
Hi @w13915984028 sorry for the delay, we had a hardware failure that took me away from this part The cluster is 3 identical nodes 64 core 252 gb ram 12tb each of storage dual 10gb nics
kubectl get pvc -A -o YAML apiVersion: v1 items:
kubectl get volume -A -o YAML apiVersion: v1 items:
kubectl get volume -A -o YAML apiVersion: v1 items:
It turns out it was a corrupted ISO, I was using the web URL download function, direct upload of a known good file remediated the issue
Hello all I just created my first cluster and am getting the following error when starting a new VM
AttachVolume.Attach failed for volume "pvc-5c7440eb-e1d3-4ad9-ac64-1ae3a569057c" : rpc error: code = Internal desc = Bad response statusCode [500]. Status [500 Internal Server Error]. Body: [message=unable to attach volume pvc-5c7440eb-e1d3-4ad9-ac64-1ae3a569057c to test3: invalid volume state to start migration attaching, code=Server Error, detail=] from [http://longhorn-backend:9500/v1/volumes/pvc-5c7440eb-e1d3-4ad9-ac64-1ae3a569057c?action=attach]
The volume shows up in volumes tab this is my first time using Harvester so please tell me what else you need and where to find it and apologies if I missed anything