Upgrading to version 1.0.8.5
Upgrade to version 1.0.8.5 is performed by IBM Support.
The system upgrade timings are limited to three levels:
- Base
- Base + 2
Upgrade | Dell/Lenovo | Approximate upgrade time |
---|---|---|
1.0.7.x to 1.0.8.5 | Dell Base + 2 | 7 hours |
1.0.8.x to 1.0.8.5 | Dell Base | 4 hours |
1.0.7.x to 1.0.8.5 | Lenovo Base + 2 | 8 hours |
1.0.8.x to 1.0.8.5 | Lenovo Base | 6 hours |
Before you begin
Upgrade prerequisites:
- Upgrade to version 1.0.8.5 is supported for systems on 1.0.7.6 or later.
System health-check:
- Do the healthcheck of the system. For more details, see CPDS IIAS System healthcheck tool.
Exception
- If you are using Cloud Pak for Data System 1.0.8, you must first apply 1.0.8.0 Interim Fix 2 before proceeding with 1.0.8.5. For further details, refer to the 1.0.8.0 Interim Fix 2 release notes.
Network setup prerequisites:
- Before you start the upgrade, setup network
yaml
file. Go to directory:/opt/ibm/appliance/platform/apos-comms/customer_network_config/ansible
- Run
yaml
check to make sure your houseyaml
file is valid:/opt/ibm/appliance/platform/apos-comms/tools/aposYmlCheck.py
- Run the following command (Enter the correct customer
yaml
file):ANSIBLE_HASH_BEHAVIOUR=merge ANSIBLE_LOG_PATH=/var/log/appliance/platform/apos-comms/house_setup.log ansible-playbook -i ./System_Name.yml playbooks/house_config.yml
Netezza prerequisites:
- It is recommended to upgrade to Netezza Performance Server 11.2.1.9.
About this task
Only the system bundle is upgraded in version 1.0.8.5.
Procedure
Results
cyclops
and the associated influxdb
container.
Container images are installed on all control nodes for high availability. When a control node goes
out of service, Platform Manager starts the cyclops
and influxdb
containers on another control node (or a connector
node).[root@mysystem-node1 ~]# for node in `/opt/ibm/appliance/platform/xcat/scripts/xcat/display_nodes.py --control`; do echo ${node}; ssh $node docker ps -a | grep -E 'cyclops|influxdb'; done
e1n1
c7d402b47de8 cyclops:4.0.2-20221114b30631-x86_64 "/scripts/start.sh" 4 days ago Exited (255) 30 hours ago cyclops
9f960b843510 influxdb:latest "/entrypoint.sh in..." 4 days ago Exited (255) 30 hours ago 0.0.0.0:8086->8086/tcp influxdb
e1n2
642f4b0b5087 cyclops:4.0.2-20221114b30631-x86_64 "/scripts/start.sh" 4 days ago Up 30 hours 80/tcp, 3000/tcp, 5480/tcp, 0.0.0.0:3333->3333/tcp, 0.0.0.0:8843->8443/tcp cyclops
177a97aaa701 influxdb:latest "/entrypoint.sh in..." 4 days ago Up 30 hours 0.0.0.0:8086->8086/tcp influxdb
e1n3
d590a49d369f cyclops:4.0.2-20221114b30631-x86_64 "/scripts/start.sh" 4 days ago Exited (137) 4 days ago cyclops
19e5f305548e influxdb:latest "/entrypoint.sh in..." 4 days ago Exited (0) 4 days ago influxdb
[root@mysystem-node1 ~]#
The ap version -s
container reflects the web
console version:[root@csr-node1 ~]# ap version -s
Appliance software version is 1.0.8.5
All component versions are synchronized.
+-----------------------------+-----------------------------------------------------------------+
| Component Name | Version |
+-----------------------------+-----------------------------------------------------------------+
| Appliance platform software | 1.0.8.5-20240820171948b1430 |
| aposcomms | ibm-apos-network-tools : 27.7.5-1 |
| | ibm-apos-named-config : 3.5.0-1 |
| | ibm-apos-dhcpd-config : 5.2.0-1 |
| | ibm-apos-udev-rules-config : 3.1.1-1 |
| | ibm-apos-network-config : 7.3.0-1 |
| | ibm-apos-common : 11.3.1-1 |
| | ibm-apos-chrony-config : 5.0.1-1 |
| apupgrade | 1.0.8.5-20240809024938b1150 |
| callhome | 1.1.28.0-20240610123646b1 |
| containerapi | 1.0.23.0-20240610122323b16475 |
| cyclops | 4.0.2-20230428b3082 |
| docker-upgrade | oci-systemd-hook : 0.2.0-1 |
| | oci-umount : 2.5-3 |
| | oci-register-machine : 0-6 |
| | atomic-registries : 1.22.1-29 |
| | docker-debuginfo : 1.13.1-161 |
| | docker-common : 1.13.1-209 |
| | docker-client : 1.13.1-209 |
| | docker-rhel-push-plugin : 1.13.1-209 |
| | docker : 1.13.1-209 |
| | containers-common : 0.1.40-12 |
| | container-storage-setup : 0.11.0-2 |
| | container-selinux : 2.119.2-1.911c772 |
| | python-pytoml : 0.1.14-1 |
| gpfs | 5.1.2-7 |
| gpfsconfig | 1.0.8.5-20240705071820b220 |
| hpi | hpicfg : 2.0.4.4-20240610152534b1 |
| | hpi-lenovo-node-firmware : 1.8.0.2-20240613145357 |
| | hpi-cumulus-mgtsw-firmware : 2.0.0.1-20240613145357 |
| | hpi-cumulus-switch-firmware : 2.0.0.1-20240613145357 |
| | hpi-cumulus-fabspine-firmware : 2.0.0.1-20240613145357 |
| | hpi-cumulus-fabsw-firmware : 2.0.0.1-20240613145357 |
| | hpiutils : 2.0.4.4-20240610152626b1 |
| | hpi-x86_64-image : 2.0.4.5-20240610152813b1 |
| | hpi-dell-node-firmware : 1.8.0.1-20240613145357 |
| | hpi-software : 1.0.8.5-20240821001125b44 |
| | dct : 1.0.7.8-20240610185936b1 |
| magneto | 1.0.28.4-20240805183103b930 |
| mellanox | 1.0.8.0 |
| mvcli | 2.3.10.1095 |
| nodeos | 1.0.8.5-20240705061826b220 |
| platformbackups | 1.0.20.0-20240610122316b16473 |
| psklm | 1.0.24.0-20240620080617b2 |
| solarflare | 4.15.10.1002 |
| supporttools | 1.0.23.11-20240610152352b16470 |
+-----------------------------+-----------------------------------------------------------------+
Firmware post-upgrade steps
After you finish your 1.0.8.5 upgrade process, you must ensure that your firmware is also upgraded.