Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: MountVolume.WaitForAttach failed for volume, no fc disk found #3588

Open
kma67 opened this issue Jan 11, 2025 · 4 comments
Open

Error: MountVolume.WaitForAttach failed for volume, no fc disk found #3588

kma67 opened this issue Jan 11, 2025 · 4 comments
Labels

Comments

@kma67
Copy link

kma67 commented Jan 11, 2025

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

@kma67 kma67 added the kind/bug label Jan 11, 2025
@awels
Copy link
Member

awels commented Jan 27, 2025

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.

@kma67
Copy link
Author

kma67 commented Jan 27, 2025

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

@kma67
Copy link
Author

kma67 commented Jan 31, 2025

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"

@kma67
Copy link
Author

kma67 commented Jan 31, 2025

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants