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
s
stocky-beard-10620
06/20/2022, 5:44 PMHello! I'm in the process of upgrading to 1.3.0 (I'm deploying with Helm), but after upgrading, almost all my volumes are stuck in
Attachingl
late-needle-80860
06/20/2022, 5:51 PMis
kubectl describe …Is
kubectl describeAnd how many vols do you have? Thinking if this could be a … wait some more and the
instance-managerengine-managers
stocky-beard-10620
06/20/2022, 5:58 PMThe
kubectl describe ...timed out waiting for the conditiondescribeEventsl
late-needle-80860
06/20/2022, 5:59 PM15 is kinda nothing … so shouldn’t be that. And nothing obvious in the stdout / container logs of whatever workloads?
s
stocky-beard-10620
06/20/2022, 6:00 PMI'm combing through them but I don't think I'm going to find much because these workloads can't even start without the volumes attached
l
late-needle-80860
06/20/2022, 6:05 PMah yeah okay … fair enough. Makes sense.
And what about if you port-forward to the Longhorn UI … are the nodes Healthy and schedulable?
s
stocky-beard-10620
06/20/2022, 6:08 PMThe Longhorn nodes are healthy and scheduleable, but one thing I'm noticing is that all the replicas in all the nodes are either
FailedStoppedUnknownThere's also nothing on the
instance-manager-e-rAlso, if I open a given volume, it shows me that the only available replica is stopped but assigned to an instance manager with a name that doesn't match any of the
instance-manager-r-*Is it possible that during the upgrade the connection between replicas an instance-managers got lost or out of sync and now I have to do it manually on the custom resource objects directly?
Let me start a new thread with this because I think this looks like a potential root cause...
l
late-needle-80860
06/20/2022, 6:54 PMyeah new thread