Container Storage Modules

After a reboot, Windows non-clustered devices were not coming online when using PowerShell to online the devices. Coincidentally, the AppSync plugin was recently installed.

This Article describes methods for identifying and treating problems related to the media database, as well as best practices for maintenance and protection.

This article explains the ways to get support for the Container Storage Modules (CSM) and Container Storage Interface (CSI) Drivers.

Replicated Persistent Volumes (PVs) and DellCSIReplicationGroups (RGs) occasionally do not get deleted when issued relevant Kubernetes deletion commands. SyncIQ policies on PowerScale arrays can also improperly persist after their related RG is deleted.

Container Storage Modules Operator: After driver controller down scaling, 'Available' attribute causes incorrect failure status report in deployment.

When "skipCertificateValidation" is false for Container Storage Modules Authorization in the driver custom resource, the Authorization sidecar proxy (karavi-authorization-proxy container) does not validate the certificate.

When the Container Storage Modules Operator is installed from the OpenShift Console Operators view (Operator Lifecycle Manager (OLM), the Operator continuously is unresponsive due to a missing custom resource.

The Container Storage Module (CSM) Operator is not calculated status when the Container Storage Module (CSI) driver is installed as a stand-alone.

In Container Storage Modules (CSM) 1.9.1 when Application Mobility is installed as a stand-alone, the CSM status is marked as fail even though it succeeds.

In Container Storage Module (CSM) Operator v1.4.1, the Authorization proxy CSM object status stays in a failed state even when pods are successful.

In CSM Operator v1.4.1, the CSM object associated with a driver deployment stays in a failed state even when the deployment succeeds.

In Container Storage Modules (CSM) Operator v1.4.1, the CSM object associated with a driver deployment stays in a failed state even when the deployment succeeds. This occurs with PowerScale Observability.

Container Storage Modules (CSM) PowerFlex node pods are stuck at init:0/2 after hosts were reboot due to some changes applied on them.

The Container Storage Interface (CSI) Driver shows "can't match block device with provided HCTL"(Host Channel Target Lun). This occurs with PowerStore array over Fiber Channel (FC) on CoreOS hosts in OpenShift. This occurs when the LUN ID(logical unit number) is greater than 255 due to a CoreOS limitation.

How to enable Persistent Volume Claim (PVC) volume usage metrics in Kubernetes and Red Hat OpenShift.

Dell EMC Container Storage Modules Security Update for GoGo Protobuf Vulnerability.

Welcome to the Avamar Data Migration enabler (ADMe) landing page.

This article explains how to assign an Initial Company Administrator.

Avamar NDMP (Network Data Management Protocol) backups of NetApp fail with Signal 11 (segmentation fault) when the NetApp inode list for backup history exceeds RAM. Fix: reduce dataset size or enable stream-disk-buffer.

When backing up NetApp volumes, the backup fails in the initialization phase. When avtar tries to read the inode.dir.map from previous backup, it terminates with Fatal signal 11 due to high memory usage.

Dell Container Storage Modules remediation is available for gofsutil that may be exploited by malicious users to compromise the affected system.

Avamar Proxy Deployment Manager is failing during the Create Recommendation process. - Error connecting to mc service.

When two separate networks are configured on PowerStore, one for iSCSI and a second for NVMeTCP, the Container Storage Interface (CSI) Driver 2.9.0 fails to mount volumes using the second network.

After filling all the parameters, and clicking the Apply button, an error message is received after 4-5 minutes when configuring a new LDAP in AppSync. The CPU and RAM remain high. Error message received when LDAP configuration fails: org.jboss.resteasy.client.exception.ResteasyInternalServerErrorException: HTTP 500 Internal Server Error

Dell CSM/CSI Drivers uses Kubernetes and Sidecars open-source solutions and are interdependent. Any new sidecar versions released by Kubernetes is not considered supported by engineering unless it is tested/certified by the cert-csi tool https://dell.github.io/csm-docs/docs/csidriver/installation/test/certcsi/ Dell CSM/CSI team. The quarterly releases of CSM/CSI-Drivers always contain the latest revisions of the K8S sidecars available ahead of the code freeze of the CSM/CSI-Drivers prior to the public release. If you want to use the latest sidecars version which are recently released and are not incorporated by the CSM/CSI Drivers yet then they can update the sidecars versions in the following file and build their own local image using following commands:

In CSM Operator v1.4.2, the CSM object associated with an application-mobility deployment occasionally stays in a failed state even when the deployment succeeds.

Container Storage Modules (CSM) and Authorization Container Storage Interface (CSI) Driver show snapshot "map denied"

The Container Storage Interface (CSI) Driver for PowerScale shows that "copy volume failed" when using the volume cloning feature.

Client creation wizard fails with host is not valid error due to name resolution issues.

The `ddbmdb2adutil LOG` command is slow to update the retrieved log.