#Can not create volumes on OpenShift

1 messages · Page 1 of 1 (latest)

sharp wagon
#

Hi All,

We are trying to create a volume with ISCSI.

time="2024-11-21T23:09:43Z" level=warning msg="Failed to create the volume on this pool." backend=ontap-lab-iscsi-1-backend backendUUID=2e59fcc9-91d0-455d-a6ea-bd082b449e3d error="backend cannot satisfy create request for volume trident_pvc_30bf2e44_1946_4529_8cac_78a198fa0db8: (ONTAP-SAN pool aggr1/aggr1; error: [GET /storage/aggregates][403] aggregate_collection_get default &{Error:0xc001719110})" logLayer=core pool=aggr1 requestID=75f06a67-9755-43c7-86c9-7ebf0ceafa23 requestSource=CSI volume=pvc-30bf2e44-1946-4529-8cac-78a198fa0db8 workflow="volume=create"

apiVersion: trident.netapp.io/v1
kind: TridentBackendConfig
metadata:
labels:
TridentBackendSelector: ontap-lab-iscsi-1-backend
app.kubernetes.io/instance: cluster-storage
name: ontap-lab-iscsi-1-backend
namespace: trident
spec:
credentials:
name: ontap-trident-creds
dataLIF: 10.10.200.138
managementLIF: 10.10.200.139
storageDriverName: ontap-san-economy
svm: svm_iscsi
version: 1

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
labels:
app.kubernetes.io/instance: cluster-storage
name: ontap-lab-iscsi-1
parameters:
media: hdd
provisioner: csi.trident.netapp.io

Any ideas?

We are using ONTAP Select in our Lab

#

Can not create volumes on OpenShift

fervent estuary
#

Is aggr1 perhaps not of hdd type?
Is this a new setup or have creation succeeded previously?

solemn jasper
#

what credentials do you use to connect? Does the user have role admin (if you connect to the cluster mgmt LIF) or vsadmin (if you connect th the SVM mgmt LIF)?

sharp wagon
#

This is a new setup. We are running ONTAP Select in our Lab a proof of concept. We have given openshift vsadmin credentails to our iSCSI SVM and we have a separate mgmt LIF in the iSCSI SVM

sharp wagon
#

looks like ONTAP select reports its disk as VMDISK

#

a1lab-ntap-cls01::> disk show
Usable Disk Container Container
Disk Size Shelf Bay Type Type Name Owner

NET-1.1 1.44TB - - VMDISK aggregate aggr1 a1lab-ntap-cls01-01
NET-1.2 66.93GB - - VMDISK aggregate aggr0_a1lab_ntap_cls01_01 a1lab-ntap-cls01-01
2 entries were displayed.

solemn jasper
#

did you add the aggregate to the SVM?

next sierra
#

aggr1 should be included in the SVM aggr-list

sharp wagon
#

the aggregates are assigned to the SVM

#

i even did it again

#

but Openshift is still bombing out

sharp wagon
solemn jasper
#

error: [GET /storage/aggregates][403]

I still think it is some kind of permission issue (HTTP 403 is "permission denied"). please double-check that you have the correct username and password in your k8s credential

fervent estuary
#

and changing the StorageClass media parameter to "vmdisk" did nothing?

sharp wagon
#

ok.,. managed to log a support case with NetApp and they came back with this

#

I see the Storage class is not mapped correctly. Hence it is unable to provision volumes.
You shall recreate the storage class with below example:

cat storage-class-sanvol.yaml

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: ontap-lab-iscsi-1
provisioner: csi.trident.netapp.io
reclaimPolicy: Retain
parameters:
backendType: "ontap-san-economy"
storagePools: “ontap-lab-iscsi-1-backend:aggr1”
allowVolumeExpansion: true

#

soon as we update that.. boom.. iSCSI now working