PowerStore: Cluster name change and then verifying data replication connection may lead to node reboot

• Replication is configured between two clusters.
• Changing a cluster name and then later on invoking verify and update may lead to a node reboot.
• Verify and update is located under Protection > Remote Systems, choose relevant remote system and under More Actions choose Verify and Update.

• This issue affects PowerStoreOS 3.0 and later.
• Due to a software issue when changing the cluster name and running verify and update, a stale object is created in the replication stack. 
• The stale object should not cause any issue unless the article PowerStore: After Transport Update to TCP, Replication Sessions are in the System_Paused State (Dell Technologies Correctable) was followed to fix an issue related to changing transport type to TCP.
• As a result of fixing the issue above, a node may unexpectedly reboot.

This issue was addressed in PowerStoreOS version 4.1 (or later). This issue was also addressed in version 4.0.0.2.

Workaround

With earlier versions, contact Dell Technical Support to confirm this issue has occurred. Reference this article in the Service Request for expedited handling.