Version 1.0.8.2 release notes

Cloud Pak for Data System version 1.0.8.2 is the next version after 1.0.8.1 and is intended for Netezza Performance Server customers only. 1.0.8.2 comes with firmware upgrade enhancements, security improvements, and STIG compliance.

Upgrading

The upgrade procedure is performed by IBM Support.

Do not upgrade to 1.0.8.2 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

Upgrade

You can now upgrade to Cloud Pak for Data System 1.0.8.x versions from 1.0.7.3 onwards. For more details on upgrade, see Upgrading Cloud Pak for Data System.

Security

STIG compliance

Cloud Pak for Data System version 1.0.8.2 comes with more security improvements and STIG compliance. Nessus CAT-II compliance failures are also addressed in 1.0.8.2 release. For more details, see:

Security vulnerabilities

Important security vulnerabilities are addressed in 1.0.8.2. The CVEs included in 7.9.23.06.SP22 and 7.9.23.04.SP21 are covered in 1.0.8.2. For the CVE lists, see:

Firmware

Cumulus OS version 3.7.16: Cloud Pak for Data System version 1.0.8.2 comes with updated Cumulus OS version 3.7.16 on all switch types.
Draft comment: arun.c.r@ibm.com
https://github.ibm.com/privatecloud-ap/cpds-issues/issues/4229

Networking

Node-specific IP and application floating IP configuration: With Cloud Pak for Data System version 1.0.8.2, you can specify unique hostnames and node-specific IPs for connector nodes. Also, you can specify the VIP (application floating IP) and application FQDN resolve to the connector node. For more details, see Configuring nodes with external IPs and application floating IP.
Draft comment: arun.c.r@ibm.com
https://github.ibm.com/privatecloud-ap/cpds-issues/issues/4338

Software components

Recommended to upgrade to Netezza Performance Server 11.2.1.9.

Resolved issues

Serviceability

Fixed the issue with Lenovo SD530 that caused failure to collect the enclosure Fast Failure Data Collection (FFDC) from the System Management Module (SMM).
Draft comment: arun.c.r@ibm.com
https://github.ibm.com/privatecloud-ap/cpds-issues/issues/3301
Removed plugin for mlxlink command from fabric and spine switches. The mlxlink collection for fabric and spine switches is already part of cl-support collection.
Draft comment: arun.c.r@ibm.com
https://github.ibm.com/privatecloud-ap/cpds-issues/issues/4193
Enhanced the apdiag command to ensure the comprehensive collection of HPI logs.
Draft comment: arun.c.r@ibm.com
https://github.ibm.com/privatecloud-ap/cpds-issues/issues/4235

Platform manager

Fixed the issue that caused the failure of alert emails trigger through SMTP.
Draft comment: arun.c.r@ibm.com
https://github.ibm.com/privatecloud-ap/cpds-issues/issues/4295
Fixed the issue with SNMP communication not taking the right gateway.
Draft comment: arun.c.r@ibm.com
https://github.ibm.com/privatecloud-ap/cpds-issues/issues/4333
Fixed the issue with disabling NVMe drives on Dell systems.
Draft comment: arun.c.r@ibm.com
https://github.ibm.com/privatecloud-ap/cpds-issues/issues/4377

Upgrade

After an IF or SP upgrade, the ap version –s command now displays the correct version of the IF or SP applied on the system. Updated component_version_cronjob.py to keep track of the IF or SP upgrade versions.
Draft comment: arun.c.r@ibm.com
https://github.ibm.com/privatecloud-ap/cpds-issues/issues/4200
Updated the upgrade framework to report any failure that occurs during switch firmware upgrade. This includes both fabric (fabsw) and management (mgtsw) switches.
Draft comment: arun.c.r@ibm.com
https://github.ibm.com/privatecloud-ap/cpds-issues/issues/4188
Updated the upgrade framework to monitor SPU regen activity before initiating firmware upgrade to avoid any failures while restarting NPS.
Draft comment: arun.c.r@ibm.com
https://github.ibm.com/privatecloud-ap/cpds-issues/issues/4268
Updated the firmware upgrade framework to ensure NFS is online before attempting to start NPS.
Draft comment: arun.c.r@ibm.com
https://github.ibm.com/privatecloud-ap/cpds-issues/issues/4399
Fixed the issue with --upgrade-apupgrade to copy python3 dependencies directory to control nodes under /install/app_img/ only.
Draft comment: arun.c.r@ibm.com
https://github.ibm.com/privatecloud-ap/cpds-issues/issues/4269

Known issues

Cloud Pak for Data System version 1.0.8.2 does not support NRS.

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

Upgrade might fail during precheck for systems that have connector nodes with NPS

During upgrade to 1.0.8.2 or greater (and any version of 1.0.8.x that allows CN as master), the upgrade might fail with the following error:

                           LOGGING FROM: yosemite_bundleupgradechecker.py:ensure_shared_storage_is_up:444
2024-10-14 11:58:18 INFO: Checking if e1n1 is the hub.
                           LOGGING FROM: yosemite_bundleupgradechecker.py:check_e1n1_is_hub:462
2024-10-14 11:58:18 ERROR: e1n1 must be set as both the master and hub node prior to starting upgrade.
                           LOGGING FROM: yosemite_bundleupgradechecker.py:check_e1n1_is_hub:464
2024-10-14 11:58:18 TRACE: In method logger.py:log_error:142 from parent method yosemite_bundleupgradechecker.py:check_e1n1_is_hub:464 with args
                               msg = e1n1 must be set as both the master and hub node prior to starting upgrade.


                           LOGGING FROM: yosemite_bundleupgradechecker.py:check_e1n1_is_hub:464
2024-10-14 11:58:18 FATAL ERROR: Prerequisite system checks failed

Workaround

Run the following command to check current parameter settings on node e1n1:

ap config --list params

Example:

User config
+--------------------+-------+
| Param              | Value |
+--------------------+-------+
| allow_cn_as_master | True  |
+--------------------+-------+

Run the following command to set the allow_cn_as_master parameter to False:

ap config --set params allow_cn_as_master=false

The message will be displayed as:

Updated successfully. Changes will be effective after platform manager restart.

Run the following command to verify that the parameter allow_cn_as_master is set to False:
```
ap config --list params
```
The message will be displayed as:
```
All parameter values are default
```
Run the following commands to do the platform stop or start process and monitor ap state -d status:
```
[root@NPS-PROD-01-e1n1:]$ apstop -p
```
```
[root@NPS-PROD-01-e1n1:]$ apstart -p
```
Check that the ap state -d status shows Ready/Ready/Active. If ap state -d status shows that the application is Stopped, run the following command and confirm that ap state -d status shows Ready/Ready/Active:
```
apstart -a
```

Run the following conman to make sure that the node e1n1 is set as the master node:

ap state -d

The message will be displayed as:

+-------------------+---------+-------------+-----------+-----------+--------+---------------+---------------+
| Node              |   State | Personality | Monitored | Is Master | Is HUB | Is VDB Master | Is NRS Master |
+-------------------+---------+-------------+-----------+-----------+--------+---------------+---------------+
| enclosure1.node1  | ENABLED | CONTROL     |       YES |       YES |    YES |            NO |            NO |
+-------------------+---------+-------------+-----------+-----------+--------+---------------+---------------+

NPS container is Online on Connector node

Do the apupgrade precheck before proceeding with the upgrade.
Once the upgrade is completed, reverse all the changes.

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