The following table lists known issues and limitations that exist in PowerFlex 3.6.0.2.
Issue number & SR number | Problem summary | Workaround |
---|---|---|
SCI-62961 | Disk slot information for PowerEdge nodes introduced in PowerFlex 3.6 does not work on R650/R6525/R750 nodes with HBA355. | Use iDRAC or perccli to get the disk slot information. |
Issue number & SR number | Problem summary | Workaround |
---|---|---|
SCI-58953 | When running the PowerFlex Gateway on an Internet Explorer 11 browser, LIA Authentication gets stuck in "Loading..." status when retrieving system topology. | Use Chrome or Firefox browsers to perform this action. |
SCI-58471 | PowerFlex Gateway Tomcat log rotations do not work after an upgrade. At build time, the "server.xml" file is defined as a "noreplace-config file" in the RPM. During an upgrade, the RPM mechanism will automatically detect if the file was previously edited or not. If the file was edited, it will not be overwritten during upgrade, and the new file will be created with the ".rpmnew" suffix. | Edit the file "server.xml" manually, and change the log rotation rules. For more information, see the PowerFlex Troubleshooting Guide, "Some PowerFlex Gateway log files fail to rotate" topic. |
SCI-57810 | The PowerFlex Gateway Maintenance operation screen might show an invalid LIA authentication for a containerized SDC when connecting to the system. This should appear as N/A, and can be ignored. | None |
SCI-57304 |
PowerFlex Installer (also known as the PowerFlex Gateway) is exposed to issue HSTS Missing From HTTPS Server, CVE: https://nvd.nist.gov/vuln/detail/CVE-2017-7789 |
None |
SCI-55819 | During NDU to v3.5.1.x, in rare cases, the PowerFlex Gateway might have high CPU usage and get stuck at the upload phase. | Perform a restart of the gateway service using an SSH session to the PowerFlex Gateway:
service scaleio-gateway restart Then, in the PowerFlex Installer user interface, click Retry to continue the upgrade. |
SCI-54887 | When performing the log collection via the PowerFlex Gateway with the "exception only" check box marked, the log collection fails. | Perform log collection with the default settings via the PowerFlex Gateway. |
SCI-54799 | If Auto Collect logs is configured in the system during an NDU session, when the NDU ends, the PowerFlex Installer will display a button asking to start the first phase of the NDU, even though the previous one was completed successfully (instead of displaying the "Mark operation as done" button). | Disable auto log collection prior to starting the NDU, and run the NDU. After NDU completion, enable auto log collection again. |
Issue number & SR number | Problem summary | Workaround |
---|---|---|
SCI-60885 | When using SRA, the PowerFlex Gateway password and the MDM password must be the same. Otherwise. one of the following errors will be received in the SRM/SRA GUI:
SRA command 'discoverArrays' failed. General exception No further information available SRA command 'discoverArrays' failed. general error check logs for detail |
Change the PowerFlex Gateway and MDM user passwords at the same time. Ensure that they have admin permissions and the same password. |
Issue number & SR number | Problem summary | Workaround |
---|---|---|
SCI-64143 | Log4j is a widely used library in enterprise Java products and applications, and may be considered the most widely used Java logging library. Even if products and applications are not directly embedding Log4j, they are likely embedding another component that does.
This vulnerability is considered trivial to exploit and requires almost no technical knowledge. Since error-handling codes log the user input which triggered errors, any string which can be supplied by an attacker might be a relevant attack vector, since any layer of the codebase may log an untrusted, malicious string. This would include any strings that can be supplied without authentication. As such, it is considered among the most dangerous types of vulnerabilities - a pre-authentication remote code execution (RCE). This vulnerability is being actively exploited in the wild and is expected to have a broad impact across the enterprise space. For example, it is known to be exploitable in Apache Solr, Apache Flink, Apache Druid, and Apache Struts, among others. The PowerFlex presentation server, used for the PowerFlex GUI functionality since PowerFlex version 3.5, uses Log4j with version 2.14.1 and is impacted by this issue. |
For guidelines on how to remediate this issue, refer to the Dell Technologies Security Advisory DSA-2021-272. |
SCI-60813 | When connecting a presentation server from PowerFlex version 3.6 to a PowerFlex 3.5 system, some of the UI functionality does not work as expected. |
Use the matching version of the presentation server. In an upgrade flow, refer to the upgrade guide for guidelines about when and how to upgrade the presentation server. |
Issue number & SR number | Problem summary | Workaround |
---|---|---|
SCI-57752 |
The SDC rpm package for SLES15.X installs without any issues. However, after installation, when checking if the SDC driver's scini service is loaded, the following confusing state is returned: service scini status service: no such service scini This is a false positive status alert. |
None |
Issue number & SR number | Problem summary | Workaround |
---|---|---|
SCI-62047 | A replication failover on an RCG that is still in the initial copy phase may not present all volume members at the remote target location. | Wait for all volumes in the RCG to complete their initial copy phase before performing the failover operation for that RCG. |
Issue number & SR number | Problem summary | Workaround |
---|---|---|
SCI-63216 | When adding NVMe devices using the by-id path similar to the following: dev/disk/by-id/nvme-Dell_Express_Flash_NVMe_ P4610_1.6TB_SFF_BTLN950106ZB1P6AGN
the MDM blocks the addition due to the error: new_device_path too long, MDM supports up to 63 characters. |
Use the alternative name path in by-id location with nvme-eui in the path. For example:
/dev/disk/by-id/nvme-eui.01000000010000005cd2e448b0b75151 |
Issue number & SR number | Problem summary | Workaround |
---|---|---|
SCI-54057 | Unmapping a VMware virtual volume, and then immediately afterwards trying to overwrite its content, might generate the error: "volume n is in use". | None. Try again shortly after, because some volume operations are executed in an asynchronous fashion. |