Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-24138

kubevirt-csi consistently causes a `FailedMount` event to occur on pods

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Undefined Undefined
    • CNV v4.13.0
    • None
    • Storage Platform
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • False
    • Storage Core Sprint 231
    • None

      During the time it takes for a pvc to be hotplugged to a VMI and made accessible to the guest cluster pod, I consistently see numerous FailedMount events occur. The volume does eventually mount successfully, but we shouldn't have to see so many failures reported under normal operation.

       

      Below is the event log from a guest cluster pod that experiences this issue.

       

       

       

      Events:
        Type     Reason                  Age                From                     Message
        ----     ------                  ----               ----                     -------
        Warning  FailedScheduling        11m                default-scheduler        0/2 nodes are available: 2 pod has unbound immediate PersistentVolumeClaims. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
        Normal   Scheduled               11m                default-scheduler        Successfully assigned default/testpodwithcsi3 to vossel1-qq7v8
        Normal   SuccessfulAttachVolume  11m                attachdetach-controller  AttachVolume.Attach succeeded for volume "pvc-9cb70887-7baf-4f9c-a6ea-114a300ab74d"
        Warning  FailedMount             10m (x8 over 11m)  kubelet                  MountVolume.MountDevice failed for volume "pvc-9cb70887-7baf-4f9c-a6ea-114a300ab74d" : rpc error: code = Unknown desc = couldn't find device by serial id
        Warning  FailedMount             9m36s              kubelet                  Unable to attach or mount volumes: unmounted volumes=[pv0002], unattached volumes=[pv0002 kube-api-access-28wgp]: timed out waiting for the condition
        Normal   AddedInterface          9m24s              multus                   Add eth0 [10.133.0.22/23] from ovn-kubernetes
        Normal   Pulling                 9m24s              kubelet                  Pulling image "busybox"
        Normal   Pulled                  9m23s              kubelet                  Successfully pulled image "busybox" in 775.434867ms
        Normal   Created                 9m23s              kubelet                  Created container testpodwithcsi
        Normal   Started                 9m23s              kubelet                  Started container testpodwithcsi

              rhn-support-awels Alexander Wels
              rhn-engineering-dvossel David Vossel (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: