containerized-data-importer
containerized-data-importer copied to clipboard
kubevirt
Error: MountVolume.WaitForAttach failed for volume, no fc disk found
What happened:
Trying to use CDI DV with FC PV, working from https://kubevirt.io/labs/kubernetes/lab2 - "Experiment with the Containerized Data Importer (CDI)", no CSI driver available for storage backend so am manually proivisioning. Error is:
Error: MountVolume.WaitForAttach failed for volume "fedora-pv" (UniqueName: "kubernetes.io/fc/[3600d0231000e1b7d1feb11e82ff057fc]:3") pod "importer-fedora" (UID: "4835a411-2ab9-49b6-a4fc-ce9b8ba9f735") : no fc disk found
Expected behavior:
Properly mount volume and complete lab2 above
How to reproduce:
Manually create FC based PV Create DV as listed in lab2 docs (fails at this point)
Additional info:
Using manual storage class (set as default) -
apiVersion: storage.k8s.io/v1 kind: StorageClass metadata: name: manual provisioner: kubernetes.io/no-provisioner reclaimPolicy: Retain volumeBindingMode: Immediate
Environment:
CDI version (use kubectl get deployments cdi-deployment -o yaml): v1.61.0 Kubernetes version (use kubectl version): v1.29.4 DV specification: N/A Cloud provider or hardware configuration: Dell PowerEdge M630, 2 x Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz, 256GB RAM, bare-metal Ubuntu 24.04.1 LTS installation OS (e.g. from /etc/os-release): Ubuntu 24.04.1 LTS Kernel (e.g. uname -a): 6.8.0-51-generic Install tools: Installed via guide at https://kubevirt.io/user-guide/storage/containerized_data_importer/#install-cdi Others: N/A
Is this still a problem? If so can you paste you PV and PVC definitions? The problem appears to be that the volume cannot get attached to the node, so having those definitions will help diagnose.
Greetings Alexander,
Many thanks for the reply! Yes, I have not been able to resolve this yet. We recently moved our environment and are in the process of wrapping up installation. Once we have normal access restored, I will grab and post the PV and PVC (expected later this week).
Kevin
dv_fedora.yml:
apiVersion: cdi.kubevirt.io/v1beta1 kind: DataVolume metadata: name: "fedora" spec: pvc: storageClassName: manual accessModes: - ReadWriteOnce resources: requests: storage: 30G source: http: url: "https://download.fedoraproject.org/pub/fedora/linux/releases/40/Cloud/x86_64/images/Fedora-Cloud-Base-AmazonEC2.x86_64-40-1.14.raw.xz"
fedora-pv.yaml:
apiVersion: v1 kind: PersistentVolume metadata: name: fedora-pv labels: type: scratch spec: capacity: storage: 40G accessModes: - ReadWriteOnce persistentVolumeReclaimPolicy: Retain fc: targetWWNs: - 3600d0231000e1b7d1feb11e82ff057fc lun: 3 fsType: ext4 storageClassName: manual
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
/close
@kubevirt-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity. Reopen the issue with
/reopen. Mark the issue as fresh with/remove-lifecycle rotten./close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.