Dell PowerFlex 3.6.0.6 Release Notes

PDF

Known issues and limitations

The following table lists known issues and limitations that exist in PowerFlex 3.6.0.6.

NOTE If an issue was reported by customers, the customers' Service Request numbers appear in the "Issue number & SR number" column, and serve to correlate between customer-reported issues and the PowerFlex issue number.

Table 1. Known issues and limitations—PowerFlex Custom Node
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.

Table 2. Known issues and limitations—PowerFlex Gateway
Issue number & SR number	Problem summary	Workaround
SCI-66203 SR# v989309	The AutoComplete attribute is not disabled for passwords in form-based authentication. If the browser is used in a shared computing environment where more than one person may use the browser, "autocomplete" values may be retrieved or submitted by an unauthorized user.	None
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.

Table 3. Known issues and limitations—MDM
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 simultaneously. Ensure that they have admin permissions and the same password.
SCI-69646	By default, Python3 is installed on Ubuntu and is located in /usr/bin/python3. During the execution of the command /opt/emc/scaleio/mdm/diag/dump_and_balance_check.py --username XXXXX --password YYYYY --approve_certificate --scripts_path=/opt/emc/scaleio/mdm/diag/, the following error is encountered: bash: /opt/emc/scaleio/mdm/diag/dump_and_balance_check.py: /usr/bin/python: bad interpreter: No such file or directory .	Add "3" at the start of the Python script.

Table 4. Known issues and limitations—Presentation server
Issue number & SR number	Problem summary	Workaround
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.

Table 5. Known issues and limitations—SDC
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
SCI-69559	SDC installed with flash vSphere plug-in fails without any recovery due to end of support by VMware for ESXi 6.7.x and 6.5.x. For details, see Announcing end of general support for vSphere 6.5.x and vSphere 6.7.x (89305).	None
SCI-69251 SR# 151250184	PowerFlex SDC on ESXi versions 6.5 and 6.7 fail to install on ESXi version 6.7U3 and later. For example: root: ERROR: vmware.esximage.Errors.InstallationError: ('EMC_bootbank_scaleio-sdc-esx6.x_3.6-500.106', "('EMC_bootbank_scaleio-sdc-esx6.x_3.6-500.106', 'Could not find a trusted signer: unable to get local issuer certificate')"). For details, see vSphere VIB signing related updates (76276).	Perform these procedures to complete the installation: Option 1: Update the ESXi version to 6.7U3 or higher and try to re-install the SDC. Option 2: Use the SDC version that supports the older ESXi version, for example: PowerFlex 3.6.0.4.
SCI-71000	The SDC system service in SLES15.x is renamed to scini to maintain consistency with other Linux distributions. However, when upgrading to the latest version (scini.service), the earlier version (sdc.service) remains in use. This conflict prevents the SDC from loading.	Ensure to disable and remove the earlier SDC service manually and then, restart the latest scini service. Perform the following procedures: systemctl disable sdc.service rm /usr/lib/systemd/system/sdc.service systemctl restart scini.service

Table 6. Known issues and limitations—SDR
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.

Table 7. Known issues and limitations—SDS
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

Table 8. Known issues and limitations—vVols
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.