Version 1.0.8.5 release notes
Cloud Pak for Data System 1.0.8.5 is the next version after 1.0.8.4, and it includes bug fixes and fixes to customer-critical upgrade issues.
Upgrading
The upgrade procedure is performed by IBM Support.
Do not upgrade to 1.0.8.5 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.
Software components
The recommended NPS version is 11.2.1.9 because it has base node expansion support, which needs 1.0.8.x release. The minimum supported NPS version is 11.2.1.5.
Enhancements
This includes all customer critical upgrade fixes.
Resolved issues
Cloud Pak for Data System version 1.0.8.5 provides bug fixes and critical updates to fix customer upgrade issues.
Known issues
- Upgrade might fail due to disks are down and the filesystem cannot be mounted
- Upgrade to version 1.0.8.5 might fail because of the disks that are down and the filesystem
cannot be mounted.
- Workaround
- Run the following commands and restart upgrade.
-
mmchdisk platform start -a
-
mmchdisk ips start -a
-
mmlsdisk platform
-
mmlsdisk ips
-
mmlsnsd -X
-
- Upgrade might fail when the GPFS component upgrades
- Upgrade to version 1.0.8.5 from 1.0.7.8 on systems with connector nodes might fail when the GPFS
component upgrades.Example of tracelog:
2023-11-29 18:25:04 TRACE: run_shell_cmd_in_parallel(): running cmd systemctl restart mmsdrserv on nodes ['e5n1', 'e1n3', 'e4n1', 'e1n2', 'e1n1'] LOGGING FROM: yosemite_bundleupgradechecker.py:ensure_shared_storage_is_up:446 2023-11-29 18:35:09 TRACE: ['e5n1', 'e4n1'] RC: 1 STDOUT: [] STDERR: [A dependency job for mmsdrserv.service failed. See 'journalctl -xe' for details. ] ['e1n3', 'e1n2'] RC: 0 STDOUT: [] STDERR: [] ['e1n1'] RC: 1 STDOUT: [] STDERR: [Job for mmsdrserv.service failed because the control process exited with error code. See "systemctl status mmsdrserv.service" and "journalctl -xe" for details. ] LOGGING FROM: yosemite_bundleupgradechecker.py:ensure_shared_storage_is_up:446 2023-11-29 18:35:09 TRACE: run_shell_cmd_in_parallel_or_raise(): running cmd service gpfs start on nodes ['e5n1', 'e1n3', 'e4n1', 'e1n2', 'e1n1'] LOGGING FROM: yosemite_bundleupgradechecker.py:ensure_shared_storage_is_up:446 2023-11-29 18:45:14 TRACE: ['e5n1', 'e4n1'] RC: 1 STDOUT: [] STDERR: [Redirecting to /bin/systemctl start gpfs.service A dependency job for gpfs.service failed. See 'journalctl -xe' for details. ] ['e1n3', 'e1n2', 'e1n1'] RC: 0 STDOUT: [] STDERR: [Redirecting to /bin/systemctl start gpfs.service ] LOGGING FROM: yosemite_bundleupgradechecker.py:ensure_shared_storage_is_up:446 2023-11-29 18:45:14 ERROR: Error running command [service gpfs start] on ['e5n1', 'e4n1'] LOGGING FROM: yosemite_bundleupgradechecker.py:ensure_shared_storage_is_up:446 2023-11-29 18:45:14 INFO: You can view mmfs.log.latest log file at /var/adm/ras/ for details LOGGING FROM: yosemite_bundleupgradechecker.py:ensure_shared_storage_is_up:446 2023-11-29 18:45:14 FATAL ERROR: Prerequisite system checks failed LOGGING FROM: bundleupgradechecker.py:perform_bundle_level_checks:223 2023-11-29 18:45:14 FATAL ERROR: More Info: See trace messages at /var/log/appliance/apupgrade/20231129/apupgrade20231129175951.log.tracelog for additional troubleshooting information.
- Workaround
-
- Run mmgetstate -aLv to verify that the GPFS status is
active.
Expected output:mmgetstate -aLv
[root@gt08-node1 ~]# mmgetstate -aLv Node number Node name Quorum Nodes up Total nodes GPFS state Remarks --------------------------------------------------------------------------------- 1 e1n1 2 3 5 active quorum node 2 e1n2 2 3 5 active quorum node 3 e1n3 2 3 5 active quorum node 4 e4n1 2 3 5 active 5 e5n1 2 3 5 active
- Restart the upgrade.
- Run mmgetstate -aLv to verify that the GPFS status is
active.