Skip to main content
Version: 4.3.0

Release Notes - 4.3.0

Known Issues​

CYBER-1437: Readiness check for Pure Safe Mode​

Readiness checks cannot determine if the FlashBlade is running in Safe Mode and will report ready for failover, but will fail actual failover.

Workaround: None - failover while in Safe Mode requires assistance from Pure Support.

CYBER-1546: SMB sessions from source are not disconnected after Failover​

Client SMB sessions are disconnected but will reconnect back to a read-only file system.

Workaround: Update DNS with the new IP address of the server name used by clients to access the FlashBlade SMB shares. Manually disconnecting and reconnecting client share may be required.

CYBER-1607: License state changes to "unlicensed" when a FlashBlade is removed from inventory and re-added back in​

After removing a FlashBlade from inventory and re-adding it back, the device may show up as "unlicensed" in the list of managed devices in the License view.

Workaround: Manually set the state back to "user-licensed" and restart the SCA by logging into the Core Agent Appliance and running the command:

sudo systemctl restart sca

CYBER-1622: File system export policy names with more than 63 characters fail to replicate​

A long export name will fail to replicate from FlashBlade 4.6.3 back to 4.6.2 due to smaller name limitations on the previous version.

Workaround: Change the name of the policy to less than 63 characters.

Previous Release - 4.2.3​

Known Issues​

CYBER-1498: Configuration Replication Fails When VAST Cluster Name Contains Spaces​

An error may occur during configuration replication if the VAST cluster name contains spaces.

Workaround: Rename the VAST cluster to remove any spaces.