https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# harvester
a
This message was deleted.
g
does this pod still exist? virt-launcher-vmname-mpbn2?
q
@great-bear-19718 no. it's gone.
just posted this issue in longhorn too: https://github.com/longhorn/longhorn/issues/5388
any help would be appreciated.
g
random question but have you rebooted this node?
kubectl get node NODENAME -o yaml
q
yes
i rebooted both nodes the instance is on, and the node holding the replica
g
👍
yeah i just saw in the issue
are you please also able to generate a harvester support bundle?
or provide me one if you have already generated it
q
sure, one sec.
g
the pvc is gone
oh wait its in 
vdi
namespace
q
correct
i was gunna say. lol
g
are you able to go to harvester settings and there is a setting for support-bundle-namespaces
or additional namespaces..
add 
vdi
to it and regenerate the support bundle?
Copy code
Kubernetes Status:
    Last Pod Ref At:  2023-02-12T04:21:48Z
    Namespace:        vdi
    Pv Name:          pvc-13787ebc-7d4e-41ad-9206-de9a6adb938a
    Pv Status:        Bound
    Pvc Name:         ivanquezada-rootdisk-ossjw
    Workloads Status:
      Pod Name:          virt-launcher-ivanquezada-k8phc
      Pod Status:        Pending
      Workload Name:     ivanquezada
      Workload Type:     VirtualMachineInstance
its waiting for the pod to be launched it seems
q
i agree. but it's not launching, and if i launch it, it just hangs.
g
another support bundle with the additional namespace would be useful
q
regenerating now
g
thanks
also seems like you only have 1 replica left
for this volume compared to the default 3
q
yeah, i tried that too to see if it would dismount
didnt work.
g
i can see the error.. but no two snapshot classes with same name, i have asked the longhorn team as well
q
okay. anything i can do on my side?
g
not yet.. i will let you know
q
great. thanks!
g
Copy code
(⎈|default:longhorn-system)➜  harvester-758d56647d-wlgj2 k get engine | grep pvc-13787ebc-7d4e-41ad-9206-de9a6adb938a
pvc-13787ebc-7d4e-41ad-9206-de9a6adb938a-e-4596c93c   error     harvester-05   instance-manager-e-c2f010c0                                       4d7h
pvc-13787ebc-7d4e-41ad-9206-de9a6adb938a-e-6591f94e   error     harvester-03   instance-manager-e-50d28d2d                                       5d
i see the two engine instances
i am just checking if one can be deleted safely
q
@great-bear-19718 did you happen to find out anything?
g
yeh you should be able to delete one of the engine objects it seems
kubectl delete engine pvc-13787ebc-7d4e-41ad-9206-de9a6adb938a-e-6591f94e -n longhorn-system
q
so that released it. now it's showing as faulted. but there are no replicas to salvage it to.
g
yeah all the replicas were unfortunately unhealthy
q
so is there a way to get it to mount?
g
what does 
kubectl get replicas -n longhorn-system
show?
q
nothing for that pvc
it does still show up a a pvc, and a pv. so is there any way to get it mounted into a vm? or not really?
g
Copy code
kubectl get replica -n longhorn-system | grep pvc-13787ebc-7d4e-41ad-9206-de9a6adb938
i think this was the last replica for the pv in question
q
nothing
g
if the replica crd is gone
q
okay, i'll take a stab at it a little later. thanks!
quick question. do you think if i didnt delete some of the replicas, and kept them, but just deleted the engine, i would have a replica to salvage still?
thank you for your help with this by the way. i appreciate it
4 Views
Open in Slack
PreviousNext
Powered by