This is the release note for the 8.4.3 release and details the issues resolved in all Program Temporary Fixes (PTFs) between 8.4.3.0 and 8.4.3.1. This document will be updated with additional information whenever a PTF is released.
Note: This release only supports Spectrum Virtualize for Public Cloud on Microsoft Azure.
Note: This release is a Non-Long Term Support (Non-LTS) release. Non-LTS code levels are not intended to receive any PTFs. If issues are encountered the only resolution is likely to be upgrade to a later LTS or Non-LTS release.
For details of the new Continuous Development release strategy refer to the Spectrum Virtualize Family of Products Upgrade Planning page.
This document was last updated on 28 October 2024.
Note: Detailed build version numbers are included in the Update Matrices in the Useful Links section.
| Details | Introduced |
|---|---|
|
Automatic deletion of resources in a failed deployment. As part of deployment, you can optionally select a rollback feature that automatically deletes resources in a failed deployment. If you plan to redeploy with the same settings and resources are not removed from the failed deployment, the redeployment can also fail. Due to a limitation in the Microsoft Azure implementation, automatic deletion of resources might not be possible and manual deletion of specific resources is required. For more information, see Deleting failed deployments and resources. |
8.4.3.0 |
|
Adding Azure Managed Disk with the CLI can error or time out. This error occurs when you are adding Azure manage disks with the command-line interface when other removing or adding actions are ongoing. Due to a Microsoft Azure limitation, these commands can time out and fail. To avoid time out issues, ensure that any Azure-related process related to adding or removing managed disks is complete before issuing any more add or remove MDisk commands. For more information, see Adding cloud-based storage or Removing cloud-based storage. |
8.4.3.0 |
|
Intermittent failures when collecting logs using the snap command. Currently a known limitation exists when you use the snap command to generate logs for error resolution for IBM Spectrum
Virtualize for Public Cloud deployments on Microsoft Azure. This limitation only occurs with the CLI and affects
associated scripts. This issue is intermittent and occurs with large log files and snaps. To avoid this limitation, you
can use the management GUI or the service command, |
8.4.3.0 |
| If an update stalls or fails then contact IBM Support for further assistance | n/a |
A release may contain fixes for security issues, fixes for APARs or both. Consult both tables below to understand the complete set of fixes included in the release.
| APAR | Affected Products | Severity | Description | Resolved in | Feature Tags | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| HU02406 | All | Critical | An interoperability issue between Cisco NX-OS firmware and the Spectrum Virtualize Fibre Channel driver can cause a node warmstart on NPIV failback (for example during an upgrade) with the potential for a loss of access. For more details refer to this Flash
(show details)
|
8.4.3.1 | Interoperability | ||||||||
| HU02441 & HU02486 | All | Critical | Safeguarded Copy with DRP can cause node warmstarts and mdisk timeouts
(show details)
|
8.4.3.0 | Data Reduction Pools, Safeguarded Copy & Safeguarded Snapshots |
| Description | Link |
|---|---|
| Support Websites | |
| Update Matrices, including detailed build version | |
Support Information pages providing links to the following information:
|
|
| Spectrum Virtualize Family of Products Inter-System Metro Mirror and Global Mirror Compatibility Cross Reference | |
| Software Upgrade Test Utility |