Version 1.0.8.3 release notes

Cloud Pak for Data System 1.0.8.3 is the next version after 1.0.8.2 and is intended for Netezza Performance Server customers only. 1.0.8.3 comes with IBM Spectrum® Protect LAN-free integration with Netezza® Performance Server.

Draft comment: arun.c.r@ibm.com
TBD

Note: Cloud Pak for Data System 1.0.8.3 has all the security updates up to SP23. Future security patches (SP24 and later) can be applied.

Upgrading

The upgrade procedure is performed by IBM Support.

Do not upgrade to 1.0.8.3 if you are using Cloud Pak for Data. The upgrade path for system with Cloud Pak for Data is 1.0.7.3 > 2.0.x. For more information, see https://www.ibm.com/docs/en/cloud-paks/cloudpak-data-system/2.0?topic=system-advanced-upgrade-from-versions-10x.

What's new

IBM Spectrum Protect LAN-free integration with Netezza Performance Server: IBM Spectrum Protect is a 3rd party platform that felicities the management of Netezza Performance Server backups. Netezza Performance Server acts as a client of the IBM Spectrum Protect server. IBM Spectrum Protect offers unique capabilities for taking backups directly on SAN.; For more information, see IBM Spectrum Protect LAN-free integration with Netezza Performance Server.
Switch firmware upgrade duration information: The upgrade trace log now displays the approximate upgrade time once the upgrade process is started.
Important: When upgrading a fabsw (fabsw1a, fabsw1b, and so on), DO NOT restart hpid, reboot any switch, or CTRL-C. This process can take up to 20 minutes. The log might look as if it is stopped, but let it continue till sys_hw_config completes.
External IP on NRS nodes: With Cloud Pak for Data System 1.0.8.3, you can set up hostname and IP for NRS nodes. For more information, see External IP on NRS nodes.

Draft comment: arun.c.r@ibm.com
https://github.ibm.com/privatecloud-ap/cpds-issues/issues/4491

Software components

It is recommended to upgrade to Netezza Performance Server 11.2.1.9.

Draft comment: arun.c.r@ibm.com
NPS version to be confirmed. Also, should we update the kernel version related info (TSM-related)?

Resolved issues

Upgrade

With CPDS 1.0.8.3, the upgrade process stops if any of the managed nodes (control nodes or non-control nodes) is disabled.
Draft comment: arun.c.r@ibm.com
https://github.ibm.com/privatecloud-ap/cpds-issues/issues/4503
Fixed the issue with ap version -s command that caused missing SP version while running. The error was caused by e10n1 taking precedence over e1n1.
Draft comment: arun.c.r@ibm.com
https://github.ibm.com/privatecloud-ap/cpds-issues/issues/4231
Fixed the upgrade failure issue that happened during NPS state check. The upgrade now checks whether the fab-br0:VDB1 interface is up on the node where it intends to start NPS host container and bring it up if not.
Draft comment: arun.c.r@ibm.com
https://github.ibm.com/privatecloud-ap/cpds-issues/issues/4477
Fixed the issue with GPFS failing to discover disks after rebooting SED enabled systems.
Draft comment: arun.c.r@ibm.com
https://github.ibm.com/privatecloud-ap/cpds-issues/issues/4501
Added a fix in upgrade to bring up hub.fbond interface when the nodes come back online after a reboot.
Draft comment: arun.c.r@ibm.com
Waiting for clarity on how to document this issue.https://github.ibm.com/privatecloud-ap/cpds-issues/issues/4490

Known issues

Duplicate entries on ap fs command execution

In the case of IBM Spectrum Protect configuration, there can be duplicate entries (GPFS file system ips and platform might appear twice) as a result of the ap fs command.

[root@mysystem-node1 ~]# ap fs
(...)
Filesystems mounts
+------------+------------------+---------------------------------------------+
| Filesystem | Node             | Mountpoint                                  |
+------------+------------------+---------------------------------------------+
| ips        | enclosure1.node1 | /opt/ibm/appliance/storage/ips              |
| ips        | enclosure1.node1 | /opt/ibm/appliance/storage/ips              |
| ips        | enclosure1.node2 | /opt/ibm/appliance/storage/ips              |
| ips        | enclosure1.node2 | /opt/ibm/appliance/storage/ips              |
| ips        | enclosure1.node3 | /opt/ibm/appliance/storage/ips              |
| ips        | enclosure1.node3 | /opt/ibm/appliance/storage/ips              |
| ips        | enclosure5.node1 | /opt/ibm/appliance/storage/ips              |
| ips        | enclosure5.node1 | /opt/ibm/appliance/storage/ips              |
| ips        | enclosure6.node1 | /opt/ibm/appliance/storage/ips              |
| ips        | enclosure6.node1 | /opt/ibm/appliance/storage/ips              |
| platform   | enclosure1.node1 | /opt/ibm/appliance/storage/platform         |
| platform   | enclosure1.node1 | /opt/ibm/appliance/storage/platform         |
| platform   | enclosure1.node2 | /opt/ibm/appliance/storage/platform         |
| platform   | enclosure1.node2 | /opt/ibm/appliance/storage/platform         |
| platform   | enclosure1.node3 | /opt/ibm/appliance/storage/platform         |
| platform   | enclosure1.node3 | /opt/ibm/appliance/storage/platform         |
| platform   | enclosure5.node1 | /opt/ibm/appliance/storage/platform         |
| platform   | enclosure5.node1 | /opt/ibm/appliance/storage/platform         |
| platform   | enclosure6.node1 | /opt/ibm/appliance/storage/platform         |
| platform   | enclosure6.node1 | /opt/ibm/appliance/storage/platform         |
| tsm        | enclosure5.node1 | /opt/ibm/appliance/storage/external_mnt/SAN |
| tsm        | enclosure6.node1 | /opt/ibm/appliance/storage/external_mnt/SAN |
+------------+------------------+---------------------------------------------+

Generated: 2023-07-28 06:22:02

Draft comment: arun.c.r@ibm.com
https://github.ibm.com/privatecloud-ap/cpds-issues/issues/4486

Management switches will not be upgraded with Cloud Pak for Data System 1.0.8.3

Management switches will not be upgraded for the version 1.0.8.3. Support for these switches will be added in the next release with improved upgrade speed. Fabric switches are upgraded in this release with critical firmware fixes.

Upgrade might fail due to missing wheel (Python 3) package

For the systems with security patch 7.9.23.02.SP20 applied, upgrading to version 1.0.8 and later might fail due to missing wheel (Python 3) package.

Example of tracelog:

2024-02-10 09:58:54 INFO: nodeos:Starting Node OS component post-install steps...
                           LOGGING FROM: NodeosUpgrader.py:postinstall:166
2024-02-10 09:58:54 INFO: NodeosUpgrader.postinstall:Running nodeOS postinstall script for post upgrade configuration
                           LOGGING FROM: node_os_yosemite_postinstaller.py:run_nodeos_postinstall_script:30
2024-02-10 09:58:54 TRACE: Running command [/opt/ibm/appliance/platform/xcat/scripts/xcat/nodeos_post_actions.py].

                           LOGGING FROM: node_os_yosemite_postinstaller.py:run_nodeos_postinstall_script:31
2024-02-10 10:01:31 TRACE: RC: 1.
                           STDOUT: []
                           STDERR: [ERROR: Command ['pip3', 'install', '/tmp/python3_packages/wheel-*.whl', '-f', '/tmp/python3_packages/', '--no-index', '--prefix', '/usr'] failed with error:
                           WARNING: Requirement '/tmp/python3_packages/wheel-*.whl' looks like a filename, but the file does not exist
                           ERROR: wheel-*.whl is not a valid wheel filename.
                            More Info: See /var/log/appliance/platform/xcat/nodeos_post_action.log for details.
                           ]

                           LOGGING FROM: node_os_yosemite_postinstaller.py:run_nodeos_postinstall_script:31
2024-02-10 10:01:31 ERROR: NodeosUpgrader.postinstall:Issue encountered while running nodeOS postinstall script for configuration.
                           LOGGING FROM: node_os_yosemite_postinstaller.py:run_nodeos_postinstall_script:33
2024-02-10 10:01:31 ERROR:
                           LOGGING FROM: node_os_yosemite_postinstaller.py:run_nodeos_postinstall_script:33
2024-02-10 10:01:31 ERROR: ERROR: Command ['pip3', 'install', '/tmp/python3_packages/wheel-*.whl', '-f', '/tmp/python3_packages/', '--no-index', '--prefix', '/usr'] failed with error:
                           LOGGING FROM: node_os_yosemite_postinstaller.py:run_nodeos_postinstall_script:33
2024-02-10 10:01:31 ERROR: WARNING: Requirement '/tmp/python3_packages/wheel-*.whl' looks like a filename, but the file does not exist
                           LOGGING FROM: node_os_yosemite_postinstaller.py:run_nodeos_postinstall_script:33
2024-02-10 10:01:31 ERROR: ERROR: wheel-*.whl is not a valid wheel filename.
                           LOGGING FROM: node_os_yosemite_postinstaller.py:run_nodeos_postinstall_script:33
2024-02-10 10:01:31 ERROR:  More Info: See /var/log/appliance/platform/xcat/nodeos_post_action.log for details.
                           LOGGING FROM: node_os_yosemite_postinstaller.py:run_nodeos_postinstall_script:33
2024-02-10 10:01:31 ERROR:
                           LOGGING FROM: node_os_yosemite_postinstaller.py:run_nodeos_postinstall_script:33
2024-02-10 10:01:31 TRACE: In method logger.py:log_error:142 from parent method node_os_yosemite_postinstaller.py:run_nodeos_postinstall_script:33 with args
                               msg = NodeosUpgrader.postinstall:Issue encountered while running nodeOS postinstall script for configuration.

                           ERROR: Command ['pip3', 'install', '/tmp/python3_packages/wheel-*.whl', '-f', '/tmp/python3_packages/', '--no-index', '--prefix', '/usr'] failed with error:
                           WARNING: Requirement '/tmp/python3_packages/wheel-*.whl' looks like a filename, but the file does not exist
                           ERROR: wheel-*.whl is not a valid wheel filename.
                            More Info: See /var/log/appliance/platform/xcat/nodeos_post_action.log for details.

Workaround

Download the release bundle:

cp -r /localrepo/1.0.8.x_release/EXTRACT/system/bundle/app_img/python3_dependencies /install/app_img/

Copy the Python 3 dependencies from the bundle to /install/app_img/ on node e1n1.
Restart the upgrade.

Draft comment: rahul.kumar.p@ibm.com
https://github.ibm.com/privatecloud-ap/cpds-issues/issues/5030