Channels
academy
amazon
arm
azure
cabpr
chinese
ci-cd
danish
deutsch
developer
elemental
epinio
espanol
events
extensions
fleet
français
gcp
general
harvester
harvester-dev
hobbyfarm
hypper
japanese
k3d
k3os
k3s
k3s-contributor
kim
kubernetes
kubewarden
lima
logging
longhorn-dev
longhorn-storage
masterclass
mesos
mexico
nederlands
neuvector-security
office-hours
one-point-x
onlinemeetup
onlinetraining
opni
os
ozt
phillydotnet
portugues
rancher-desktop
rancher-extensions
rancher-setup
rancher-wrangler
random
rfed_ara
rio
rke
rke2
russian
s3gw
service-mesh
storage
submariner
supermicro-sixsq
swarm
terraform-controller
terraform-provider-rancher2
terraform-provider-rke
theranchcast
training-0110
training-0124
training-0131
training-0207
training-0214
training-1220
ukranian
v16-v21-migration
vsphere
windows
Title
g
gentle-island-98110
12/05/2022, 5:21 PMHello, I have a crash on Longhorn CSIAttacher when running 1.3.2 on IBMCloud kubernetes service 1.24. I tried with 1.3.1 and 1.3.0 to get the same crash and anything lower than that wont be supported in that version of kubernetes. Can someone point in what I should be doing to debug.
a
aloof-hair-13897
12/06/2022, 1:07 AMHi,
Which Linux distro are you running on?
Any abnormal log in Longhorn
csi-attacherlonghorn-mangerg
gentle-island-98110
12/06/2022, 1:31 AMThanks for the response. This is managed kubernetes on ibm cloud. OS isnubuntu 18 and there are no wrrros on attacher or managed. I got the above from the main kubelet logs
And also, if we go through the Longhorn UI, we can manually attach the Volume , and it creates the controller and replica/sync-agent processes properly in the instance-manager-e and instance-manager-r pods. So its somewhere in CSI that its failing but unsure how to debug further. I tried to increase --v=9 in attacher pods but no effect on it too