Fix Readme
Abstract
Welcome to IBM Storage Fusion HCI Systems 2.7.1 release. This release note contains information about IBM Storage Fusion deployments.
Content
From the 2.7.x release onwards, the documentation is hosted in separate locations for IBM Storage Fusion and IBM Storage Fusion HCI variants to cater to audience-specific information. To view earlier documentation versions of the product, see https://www.ibm.com/docs/en/storage-fusion.
- IBM Fusion Data Foundation 4.14
- Global Data Platform 5.1.9.1
- IBM Data Cataloging service 2.1.4
- Backup and Restore service 2.7.1
- For supported IBM Cloud Paks versions, see IBM Cloud Paks support for IBM Storage Fusion.
| Ticket No. | Description | Severity |
| 24734 |
DHCP reservations for HCI nodes are made using mac address of first baremetal interface. However, sometimes, baremetal bond uses mac address of second baremetal interface to send out DHCP requests which are not served by DHCP server since mac does not match, resulting localhost hostname assignment to node. This has been resolved in HCI 2.7.1 by fixing baremetal bond mac to mac address of first baremetal interface. |
Major |
| 15515 |
Changes were made to hide the tips numactl_not_installed in Global data platform service to prevent misleading warning. |
Normal |
| 26010 | A change was made to fix the baremetal bond mac address to the first baremetal interface of a node to avoid the mac race condition. | Major |
| 26020 |
DHCP reservations for HCI nodes are made using mac address of first baremetal interface. However, sometimes, baremetal bond uses mac address of second baremetal interface to send out DHCP requests which are not served by DHCP server since mac does not match, resulting localhost hostname assignment to node. This has been resolved in HCI 2.7.1 by fixing baremetal bond mac to mac address of first baremetal interface. |
Major |
| 27864 | Changes were made to display the node firmware version on Fusion GUI with the firmware version value from the ComputeMonitoring CR instead of the UpdateManagers CR if the firmware upgrade operation is complete, to prevent the firmware version from displaying blank. | Normal |
| 27383 | IMM FFDC logs were not being collected due to a closed SFTP port. Default node configurations have been updated to ensure IMM.SFTPPortControl=Open | Major |
| 25674 | Adding nodes to the OCP cluster failed due to the absence of the IBM serial number. Despite this, the compute operator would still successfully upsize the node. The appropriate tag within the product has been set to ensure the serial number is properly assigned. | Minor |
| 26921 | Legacy Backup & Restore Uninstall script updated to reflect correct CR status. | Normal |
| 27768 |
When authenticating by using Single Sign-On (SSO), the UI login screen may hang when using some identity providers. This has been fixed in 2.7.1 |
Normal |
| 27840 | The metrics exporter container in mongodb pods sometimes take a while to start, causing the container to fail the liveness probe check and the pod to restart. This can cause mongodb replicaset configuration to be in an incomplete state if the restart happens while it is being configured. Consequently, the readiness probes fails because the pods are not configured as primary or secondary which leads to Backup and Restore install being stuck. This has been fixed in 2.7.1 | Major |
| 27033 | The Storage Fusion "ibm-backup-restore" namespace should not be shown in the list of applications that are eligible for backup. This fix will prevent that application from appearing with other applications as a candidate for backup. | Major |
| 27909 | Changes were made to adjust default settings in Kubernetes Operator Pythonic Framework package to prevent API flooding in case of errors or disconnects. | Normal |
|
29475 |
Adjusted the transaction-manager container to enable OpenSSL to accept intermediate CAs in the trust store to be treated as trust anchors, in the same way as the self-signed root CA certificates. This makes it possible to trust certificates issued by an intermediate CA without having to trust its ancestor root CA. | Critical |
| 29458 | Changes made to obtain BSL information from the Backup CR instead of the Backup policy. This will prevent restore failures if the backup policy is removed. | Major |
| 26587 | A change was made to remove k8s name validation for link names as it is not required. Going forward in fusion-ui v2.7+ this will no longer be an issue because the UI is matching the CLI validation regarding the link name. | Normal |
| 27145 | The limits of the memory manager container have been increased for some of the fusion operators to resolve the pod being terminated due to the OOMKilled errors. | Major |
| 23428 | Changes were made to the log package upload experience in the Fusion UI to allow the user to provide both a severity and a text description when creating a new support ticket. | Major |
| 25260 | Intermittently submariner gets uninstalled in Fusion 2.6.1 and earlier releases due to version incompatibility. In Fusion 2.7.1, OCP has been upgraded to 4.12 and Submariner has been upgraded to 0.15.2 to resolve the issue. | Major |
Related Information
Was this topic helpful?
Document Information
Modified date:
15 December 2023
UID
ibm17080125