Release notes

Dell Container Storage Modules (CSM) release notes for replication

Release Notes - CSM Replication 1.4.0

New Features/Changes

Fixed Issues

Github ID	Description
523	PowerScale: Artifacts are not properly cleaned after deletion.

Known Issues

Github ID	Description
753	PowerScale: When Persistent Volumes (PVs) are created with quota enabled on CSM versions 1.6.0 and before, an incorrect quota gets set for the target side read-only PVs/directories based on the consumed non-zero source size instead of the assigned quota of the source. This can create issues when the user performs failover and wants to write data to the failed over site. If lower quota limit is set, no new writes can be performed on the target side post failover. Workaround using PowerScale cluster CLI or UI: For each Persistent Volume on the source kubernetes cluster, 1. Get the quota assigned for the directory on the source PowerScale cluster. The path to the directory information can be obtained from the specification field of the Persistent Volume object. 2. Verify the quota of the target directory on the target PowerScale cluster. If incorrect quota is set, update the quota on the target directory with the same information as on the source. If no quota is set, create a quota for the target directory.

Github ID

Description

753

PowerScale: When Persistent Volumes (PVs) are created with quota enabled on CSM versions 1.6.0 and before, an incorrect quota gets set for the target side read-only PVs/directories based on the consumed non-zero source size instead of the assigned quota of the source. This can create issues when the user performs failover and wants to write data to the failed over site. If lower quota limit is set, no new writes can be performed on the target side post failover.
Workaround using PowerScale cluster CLI or UI:
For each Persistent Volume on the source kubernetes cluster,
1. Get the quota assigned for the directory on the source PowerScale cluster. The path to the directory information can be obtained from the specification field of the Persistent Volume object.
2. Verify the quota of the target directory on the target PowerScale cluster. If incorrect quota is set, update the quota on the target directory with the same information as on the source. If no quota is set, create a quota for the target directory.