PVC created for iSCSI storage class using iSCSI provisioner in pending state
yagachi opened this issue · 1 comments
Hi,
I am trying to provision storage using iSCSI provisioner for Openshift 4.3. I am following the readme
https://github.com/kubernetes-incubator/external-storage/blob/master/iscsi/targetd/openshift/README.md.
I created the secret, then deployment and then storage class. But when I try to create pvc for the storage class, it goes in pending status saying the volume has to be created manually or by the provisioner.
I am able to create a PV on Openshift without using the iSCSI provisoner. That works fine. So, I believe my iSCSI target and the connections are configured correctly.
$ oc get pvc
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
myclaim Pending iscsi-targetd-vg-targetd 3s
[admin@bastion-test22 openshift]$ oc describe pvc myclaim
Name: myclaim
Namespace: iscsi-provisioner
StorageClass: iscsi-targetd-vg-targetd
Status: Pending
Volume:
Labels: <none>
Annotations: volume.beta.kubernetes.io/storage-class: iscsi-targetd-vg-targetd
volume.beta.kubernetes.io/storage-provisioner: iscsi-targetd
Finalizers: [kubernetes.io/pvc-protection]
Capacity:
Access Modes:
VolumeMode: Filesystem
Mounted By: <none>
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal ExternalProvisioning 15s (x2 over 19s) persistentvolume-controller waiting for a volume to be created, either by external provisioner "iscsi-targetd" or manually created by system administrator
Some more info from the container:
[admin@bastion-test22 openshift]$ oc exec -it iscsi-provisioner-1-s9dx7 -- bash
bash-4.2$ df -H
Filesystem Size Used Avail Use% Mounted on
overlay 129G 9.8G 119G 8% /
tmpfs 68M 0 68M 0% /dev
tmpfs 4.2G 0 4.2G 0% /sys/fs/cgroup
shm 68M 0 68M 0% /dev/shm
tmpfs 4.2G 3.2M 4.2G 1% /etc/passwd
/dev/mapper/coreos-luks-root-nocrypt 129G 9.8G 119G 8% /etc/hosts
tmpfs 4.2G 25k 4.2G 1% /run/secrets/kubernetes.io/serviceaccount
tmpfs 4.2G 0 4.2G 0% /proc/acpi
tmpfs 4.2G 0 4.2G 0% /proc/scsi
tmpfs 4.2G 0 4.2G 0% /sys/firmware
bash-4.2$ ps -aux
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
1000550+ 1 0.0 0.2 133368 23880 ? Ssl 16:04 0:00 /iscsi-controller start
1000550+ 12 0.1 0.0 11828 2972 pts/0 Ss 16:13 0:00 bash
1000550+ 18 0.0 0.0 51752 3528 pts/0 R+ 16:13 0:00 ps -aux
bash-4.2$ env | grep TARG
TARGETD_ADDRESS=206.122.130.75
TARGETD_USERNAME=admin
TARGETD_PASSWORD=ciao
Saw a similar issue #516
which was closed. I tried changing chap auth options to 'false' as mentioned by one of the commentators. That didn't work either.
# whether or not to use chap authentication for discovery operations
chapAuthDiscovery: "false"
# whether or not to use chap authentication for session operations
chapAuthSession: "false"
Any solution/help is appreciated.
Thanks.
Thanks for reporting the issue!
This repo is no longer being maintained and we are in the process of archiving this repo. Please see kubernetes/org#1563 for more details.
If your issue relates to nfs provisioners, please create a new issue in https://github.com/kubernetes-sigs/nfs-ganesha-server-and-external-provisioner or https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner.
Going to close this issue in order to archive this repo. Apologies for the churn and thanks for your patience! 🙏