Search

In csi-powerscale up through 1.4.0, NFS clients would be entered using the node FQDN if resolvable. It seems in 1.5.0, this has changed again and now entries are added using just the IP. This is fine, but it caused an issue with existing volumes, especially single-writer volumes. Volumes attached a

Does the current version of CSI driver support ASYNC /SYNC replication One of the customers looking for this feature like the cinder driver for openstack that supports repilcation for LUNS .

Problem: When deleting a pod with persistent volume attached, the pv and attachment will not delete / unattache. Steps to recreate:Before installing the csi-driver, adjust the values.yaml "volumeNamePrefix" value to anything but the default. Then install the driver. Deploy a new pod with a pv and

Hi, I'm trying to see if this CSI implementation works on IBM Power (ppc64le). After `git clone` the repo, `make build` was easy enough, and I see a 46MB binary built. However, `make unit-test` spits out a lot of "Symmetrix not found" in red in console, and that section ends like; Scenario Outline:

Hi We are trying to test isilon csi on TKC (vSphere with Tanzu 7U2). The isilon-node pods are failing with error "lookup x.x.x.x.in-addr.arpa ... x.x.x.x:53 no such host". CSI version: 1.5.0 & 1.4.0. K8S Node OS: Photon 3.0. Not sure why it is looking up for that when it already found ip, we

Problem:when deploying the unity-csi driver, running the csi-install.sh script results in pods that are in a CrashLoopBackOff state. unity-controllers = 5/5unity-nodes = 1/2 Error seems to be "Container image "k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.1.0" already present on machine" Ho

I need to put multiple networks inside the allowedNetworks parameter in this file: https://github.com/dell/csi-powerscale/blob/master/helm/csi-isilon/values.yaml This did not work: allowedNetworks: ["1.1.1.1/23", "1.1.1.2/23"] What should the syntax be for multiple networks?

I have successfully installed the csi powerscale drivers via helm on my OpenShift 4.6 cluster. All pods are up and running. I then created a storage class and created a PVC to test and am getting this error on the PVC events log: failed to provision volume with StorageClass "isilon-plain": rpc er

I would like to setup the CSI driver to use NFS volumes on NAS shares on the Unity. Currently I don't have iSCSI ports on our array. Is this a requirement? From below it seems to be that to use NFS iSCSI ports are a requirement ? Requirements Install Kubernetes or OpenShift  Configure

Hi. Have a new issue. The first was solved by creating a correct secret. Now my controller pods star and get Ready, but the node pods go in to CrashLoop complaining on not able to do reverse DNS lookup. time="2021-03-30T06:44:31Z" level=debug msg="/csi.v1.Identity/GetPluginInfo: REP 0391: Name=cs

I have a customer having issues upgrading the CSI Driver from 1.3 to 1.4. The problem is the security people dont allow access to TLS 1.3 on the firewall, so they can do an online upgrade. They tried doing the offline bundle, but they are still being requested to access online which is still block

Is there any way to run csi-powerscale driver in nodes different from workers? I have tried labeling infra nodes as “csi-isilon.dellemc.com/XX.XX.XX.XX=csi-isilon.dellemc.com” and enabling CustomTopology, but it did not work as it keeps trying to use only worker nodes.

Hi, we were trying to do pure NFS share with Unity in Kubernetes 19 using csi-unity using 3 master and 3 worker nodes on bare metal. We have installed Dell EMC UnityVSA for testing purposes before we wanted to do it in production. We have watched videos and study this community closely but we we

I would like to ask about if I can install csi-powerscale with docker community edition with k8s 1.7? does csi-powerscale supports docker community edition?

Our environment didn't have DNS and there is no plan to use DNS for storage zone. When using CSI plugin with Isilon, it keep filled in Kubernetes node FQDN in client filed. I would like to know if CSI plugin 1.3 support using Kubernetes node IP address instead. If it support, how can I configure it?

Hi Experts, I'm deploying a pod on Unity storage using iSCSI protocol. I have the pvc created, and volume looks good on Unity side.  [root@master helm]# kubectl get pvcNAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGEtest-iscsi-vol-claim Bound jij8-csivol-369833ea70 10Gi RWO unity-is

Experts, I'm trying to install CSI 1.2.0 on centOS k8s cluster, but failed. From the controller pod, seems there's authentication issue. Could you please share any idea on this? Here's my secret.json file: [root@master helm]# cat secret.json{ "storageArrayList": [{ "username": " ", "password":

Hi, I am trying to find out how to best connect our rancher 2.4.x Kubernetes v1.17.6 to an Isilon storage system. Currently we use nfs-client-provisioner to get storage from a simple Linux NFS server exporting NFS with no-root-squash. We have Postgres helm charts running on that setup, so I am happ

Hi Team, Any plans of rolling out Openshift 4.2 operator for CSI driver ? I need to test few applications on Openshift and do some performance testing. I understand currently, we have helm support for 1.14 K8s version - https://github.com/dell/csi-vxflexos/tree/master/helm/csi-vxflexos  Any

After running the install.isilon, I see that the pods in isilon-controller-0 keeps restarting and then finally goes into crashloopbackoff: [root@localhost helm]# kubectl get pods -ANAMESPACE NAME READY STATUS RESTARTS AGEisilon isilon-controller-0 2/4 CrashLoopBackOff 12 16misilon isilon-node-4bxg