Search

Dell Developer web site certificate problems encountered today.

Dear All: I deploy a k8s cluster with 1 master and 1 worker. I've done all installation requirement from the installation guide as below. When I try to test the sample.yaml from csi driver package, everything does now work correctly https://dell.github.io/csm-docs/docs/csidriver/installation/helm/

Hi, I've been working with an under-powered PowerMax storage system (or perhaps just too much historical junk), and the CSI driver on my OpenShift cluster keeps timing out with `context deadline exceeded`. There are good days and bad days, but to work on the code for functionality, I wonder if I ca

Hi Team, when we depoly CSI driver for our product, is it possible to define ".spec.template.spec.nodeSelector" to use only specific node for CSI node plugin?

I have installed CSI Isilon Driver via Operator followinghttps://dell.github.io/csm-docs/docs/csidriver/installation/operator/isilon/ Everything is created but the pods crash: [root@ibocpbas isilon]# oc get allNAME READY STATUS RESTARTS AGEpod/isilon-controller-5c567f6b66-jcw5d 4/5 CrashLoopBackOf

I'm a bit confused by the documetation when it comes to the endpoint adress to point the CSI driver towards. The logical part for me would have been to point it towards the SmartIP, but that seems to get permission denied whatever I do. If i point it towards the DNS name we are usually using for N

Hi, We have a strange authorisation issue with Powerscale CSI driver that I am not sure where it comes from. So, we have the following setup: Isilon - OneFS 9.2.0 Separate access zone for CSI - zone-CSI (for security reasons don't want to allow System AZ access for CSI). AZ zone-CSI has base dir

Hi. When will the driver support OpenShift 4.8? Regards, Ulf

Does Dell CSI support IPv6 for control and data plane? I can't find IPv6-related support anywhere.

So, I have set up the driver and all PVCs create and bind as expected. But all the pods that are provisioned to use those PVCs end up with having access denied when trying to write to the PV or do any kind of operation. Running the latest operator with the 1.6.0 PowerScale driver towards OneFS 9.1.

We provided an existing PG name as part of input parameters and verified the name matched an existing PG on the PowerMax but CSI went ahead and created its own PG anyway. We are using CSI for PowerMax 1.5 - name: X_CSI_POWERMAX_PORTGROUPS value: PG5-Eng1-2 But created: csi-DEV-FA-4D-9-FA-2D-9-FA

when i change a statefulset yaml and submit , pods start rolling update. if one of pods container terminated and recreate in the same node, this container cannot run. apiVersion: apps/v1kind: StatefulSetmetadata:name: webspec:selector:matchLabels:app: nginx # has to match .spec.template.metadata.la

When I try to use an iSCSI-based PV, the iSCSI sessions are connected through all iSCSI interfaces of Unity. If I want to use specific interfaces, is there any options for using a specific interface? For example, if I have 4 interfaces for iSCSI on Unity, is it possible to use only 2 interfaces

Hello, My customer has k8s cluster v1.15. They want to use Unity 480F for PV in k8s. Is it available in k8s v1.15? I couldn't find support matrix of Unity CSI for k8s v1.15. For Unity CSI v1.2.1, it is stated that only v1.14 and v1.16 are supported.

I'm using this on OpenShift 4.6.6. Earlier I was running driver version v.1.3.0 for last six months and suddenly it got broken. The v1.3.0 has option to create storage-class and snapshot-class while installing the driver. Since my driver broken, i had to install new version v.1.6.0. The PODs are

By default, permission of Unity NFS filesystem is root/755, so non-root Pod cannot write the data when using Unity NFS PVC. Generally, the permission can be changed by chown and chmod using initContainer, but the permission cannot be changed through initContainer due to the Security Context Constra

Hi Gurus, - I'm setting up kubernetes cluster, and following https://dell.github.io/storage-plugin-docs/docs/installation/helm/unity/, to install CSI driver for unity. - I'm able to get the pods running: [root@master test]# kubectl get po -n unityNAME READY STATUS RESTARTS AGEsnapshot-contro

Hi, I'm trying to integrate the unity CSI driver on Kubernetes. Context : Kubernetes 1.20 on CentOS 7 or Kubernetes 1.19 on Ubuntu 20.04 (same troubles) All nodes are VMware VMs The storage is an UnityVSA CSI Driver version 1.5 iSCSI and NFS configuration the two Kubernetes clusters

Received following question To sum it up, we need you to help us to fix the following error:* ls: cannot access '/var/lib/kubelet/plugins/unity.emc.dell.com/csi_sock': No such file or directorySo provisioning new PVC is not a problem and works as expected but the wan't to know if this is a Bug o

Hi Just set up the CSI Driver on OpenShift 4.7, controllers start up without a hitch. However the isilon-node-* pods ends up in a crash loop with the following error message:   [lars@l02umesmg0998 ~]$ oc logs isilon-node-msccw -n isilon -c driver --tail=200time="2021-04-13T07:09:12Z" leve