https://rancher.com/ logo
Docs
Join the conversationJoin Slack
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
Powered by Linen
storage
  • s

    steep-family-74984

    07/27/2022, 11:37 AM
    Hi folks! Anyone using rook here?
  • f

    fresh-student-62602

    09/08/2022, 5:09 PM
    Hey guys, not sure if this is the right place to ask, if it isn't please let me know what's the right channel. Basically I'm trying to figure out the exact mechanism being used to mount volumes on the node by the local path provisioner. Normally if you issue the mount command on the node you can get a clear view of the mounts coordinated by kubernetes (mostly overlay file systems that make all the magic happen), but for the local path provisioner volumes, even when traversing all existing namespaces and checking the volumes there I could not see any mounts being used (I was grepping for the dir path value used by microk8s in this case, which is
    /opt/local-path-provisioner
    )
    p
    i
    • 3
    • 3
  • l

    little-ambulance-5584

    02/16/2023, 2:42 AM
    Anyone notice any troubles using azure-file provisioners on the newer version? One of our old local clusters used to have azurefile persistent volumes and I'm having the hardest trouble doing that on a v1.24.9 cluster.
    Warning  FailedAttachVolume  115s (x9 over 20m)  attachdetach-controller  AttachVolume.Attach failed for volume "azurefile-csi" : timed out waiting for external-attacher of <http://file.csi.azure.com|file.csi.azure.com> CSI driver to attach volume unique-volumeid3
      Warning  FailedMount         112s (x4 over 17m)  kubelet                  Unable to attach or mount volumes: unmounted volumes=[data], unattached volumes=[kube-api-access-pbntk data config]: timed out waiting for the condition
    I've tried the azure-file, azurefile-csi drivers, I continue to get a plain "timed out waiting for the condition" error with no following logs on any of the containers. It's irritating because the configuration on 1.16 was straight forward and simple. I've tried different storageaccounts and everything. Any ideas?
    a
    • 2
    • 3
Powered by Linen
Title
l

little-ambulance-5584

02/16/2023, 2:42 AM
Anyone notice any troubles using azure-file provisioners on the newer version? One of our old local clusters used to have azurefile persistent volumes and I'm having the hardest trouble doing that on a v1.24.9 cluster.
Warning  FailedAttachVolume  115s (x9 over 20m)  attachdetach-controller  AttachVolume.Attach failed for volume "azurefile-csi" : timed out waiting for external-attacher of <http://file.csi.azure.com|file.csi.azure.com> CSI driver to attach volume unique-volumeid3
  Warning  FailedMount         112s (x4 over 17m)  kubelet                  Unable to attach or mount volumes: unmounted volumes=[data], unattached volumes=[kube-api-access-pbntk data config]: timed out waiting for the condition
I've tried the azure-file, azurefile-csi drivers, I continue to get a plain "timed out waiting for the condition" error with no following logs on any of the containers. It's irritating because the configuration on 1.16 was straight forward and simple. I've tried different storageaccounts and everything. Any ideas?
All PV/PVCs show bound, and I see no errors on the kube logs or docker container logs on the worker node.
the azure storage account shows no errors in logs other than "ClientOther" error with no further details.
a

adventurous-portugal-91104

02/20/2023, 7:48 AM
Im not entirely awake just yet ☕ but have you tried to utilized Azure's storage classes ? https://learn.microsoft.com/en-us/azure/aks/concepts-storage#storage-classes
View count: 1