Dell PowerStore 5200T EMC PowerStore Release Notes for PowerStore OS Version 3 - Page 28

Issue ID MDT-410197 MDT-362809 MDT-261523 MDT-245640 MDT-163489 MDT-118394 MDT-428489 MDT-415463 MDT-408571 Functional Area Description Workaround/Resolution PowerStore Manager (GUI) PowerStore Manager (GUI) PowerStore Manager (GUI) PowerStore Manager (GUI) PowerStore Manager (GUI) PowerStore Manager (GUI) PowerStore REST API PowerStore REST API PowerStore REST API An error might occur in PowerStore Manager when you click Apply after modifying the properties of a volume and clearing the Replication Destination check box at the same time. Some text editors may append line end (\n) at the end of a certificate when opening the certificate file. The certificate is regarded as an invalid certificate due to the trailing space of the certificate. If Mozilla Firefox is used to upgrade a PowerStore cluster to PowerStore 2.0, a browser cache issue might occur that causes the names of some buttons and labels to be displayed as object names instead of the correct button or label names. When rebooting or powering off a node from PowerStore Manager, the system may not display any acknowledgement that the process has begun. The Reboot or Power Down button may still appear clickable. Despite the lack of acknowledgment, the operation will be triggered successfully after a single click of the button. When a node is replaced, the new node hardware information does not appear in PowerStore Manager immediately. Uploading an upgrade package that is larger than 4 GB with Microsoft Edge or Internet Explorer fails. When a volume or volume group are migrated from one appliance to another, and migrated back after 24 hours, both performance and space metrics data for this volume or volume group may not be retrieved via REST API as there is more than one record in the metrics migration table. If an NDU fails and a rollback occurs, REST API commands may fail to work for a period of five minutes due to the management software module failback. If you retry the upgrade within five minutes, the PreUpgrade Health Check might report incorrect alerts because the failed REST API command. If the primary appliance fails over to another appliance on a cluster with three appliances, the REST API may become inaccessible for approximately one hour. Clear the Replication Destination check box first, click Apply, and then modify the other properties of the volume. Use an editor that does not append line end (\n) at the end. For example, using Notepad works fine, but using Notepad++ to open a certificate file would require manual removal of the line end. Use a different browser such as Google Chrome, Microsoft Edge, or clear the browser cache in Firefox. For instructions, see "How to clear the Firefox cache" on the Mozilla Firefox support site. None After replacing a node, wait up to 30 minutes for PowerStore Manager to display the update. Try again with a different browser. Use the REST API or CLI to manually the delete completed migration sessions in the metrics_migration_ctx table. Wait approximately 10 minutes after the upgrade fails and then retry upgrade. None. The REST API becomes accessible again after approximately one hour. 28 Known Issues