hpe-storage / csi-driver

A Container Storage Interface (CSI) driver from HPE
https://scod.hpedev.io
Apache License 2.0
55 stars 53 forks source link

Alletra-9000 Remote Copy with Peer Persistence Synchronous Replication #398

Open chad-jones opened 2 months ago

chad-jones commented 2 months ago

I followed this guide Remote Copy with Peer Persistence Synchronous Replication Parameters to create a replication enabled StorageClass. Creating a PVC with this StorageClass results in error. It seems from the Alletra event log that invalid syntax for creatercopygroup is sent from the csi driver.

Alletra 9000 Event Log

Time       : 2024-04-18 15:03:10 CEST
Severity   : Informational
Type       : Command executed
Message    : {3paradm super <none> {{0 8}} -1 10.90.80.109:13197 5837} {creatercopygroup -usr_cpg SSD_r6_Harvester 1 cph2-sky-san-002 SSD_r6_Harvester -snp_cpg SSD_r6_Harvester 1 cph2-sky-san-002 SSD_r6_Harvester harvester-rcg cph2-sky-san-002 sync} {}

Time       : 2024-04-18 15:03:10 CEST
Severity   : Minor
Type       : Command error arguments
Message    : {3paradm super <none> {{0 8}} -1 10.90.80.109:13197 5837} Command: creatercopygroup -usr_cpg SSD_r6_Harvester 1 cph2-sky-san-002 SSD_r6_Harvester -snp_cpg SSD_r6_Harvester 1 cph2-sky-san-002 SSD_r6_Harvester harvester-rcg cph2-sky-san-002 sync Error: Could not find target cph2-sky-san-002 .

HPE CSI Driver for Kubernetes

v2.4.2

HPE Alletra 9000

Release version 9.5.11
Release Type: Extended Support Release

Component Name Version CLI Server 9.5.11
CLI Client 9.5.11
System Manager 9.5.11
Kernel 4.5.0
IO Stack 9.5.11
Drive Firmware 9.5.11
Enclosure Firmware 9.5.7
Upgrade Tool 63 (240306)

datamattsson commented 2 months ago

Thanks for reporting this. It would be best if you file a support case with HPE to get this resolved.

chad-jones commented 2 months ago

The response from HPE Support:

The issue is the CSI Driver is expecting remote array name showsys -d and the target name defined in showrcopy -d targets to be exactly same.

datamattsson commented 1 week ago

I found an internal issue logged as CON-2873 for this issue.