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
Table 1. Cloud Pak for Data System upgrade time
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:
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:
  1. Before you start the upgrade, setup network yaml file. Go to directory:
    /opt/ibm/appliance/platform/apos-comms/customer_network_config/ansible
  2. Run yaml check to make sure your house yaml file is valid:
    /opt/ibm/appliance/platform/apos-comms/tools/aposYmlCheck.py
  3. 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:

About this task

Only the system bundle is upgraded in version 1.0.8.5.

Procedure

  1. Connect to the node1 management interface by using the custom_hostname or ip values from your System_Name.yml
  2. Check for the hub node by running ap node -d and ensuring that the entry for e1n1 has YES for both Is Master and Is HUB.
    ap node -d
    Output:
    [root@e1n1 ~]# ap node -d
    +------------------+---------+-------------+-----------+-----------+--------+---------------+---------------+
    | Node             |   State | Personality | Monitored | Is Master | Is HUB | Is VDB Master | Is NRS Master |
    +------------------+---------+-------------+-----------+-----------+--------+---------------+---------------+
    | enclosure1.node1 | ENABLED | CONTROL     |       YES |       YES |    YES |            NO |            NO |

    If either Is Master or Is HUB read NO, the master/hub must be moved to e1n1 before the upgrade can begin. If e1n1 is not the master/hub, 1.0.8.5 upgrade will error out with a message to that effect.

  3. Download the system bundle from Fix Central and copy it to /localrepo on e1n1.
    Note: The upgrade bundle requires a significant amount of free space. Make sure that you delete all bundle files from previous releases.
  4. From the /localrepo directory on e1n1, run:
    mkdir 1.0.8.5_release
    and move the system bundle into that directory. The directory that is used here must be uniquely named - for example, no previous upgrades on the system can have been run out of a directory with the same name.
  5. Optional: Run upgrade details to view details about the specific upgrade version:
    apupgrade --upgrade-details --upgrade-directory /localrepo --use-version 1.0.8.5_release --bundle system
  6. Before you start the upgrade process, depending on your requirements:
    • Run the preliminary checks with --preliminary-check option:
      apupgrade --preliminary-check --upgrade-directory /localrepo --use-version 1.0.8.5_release --bundle system
      If you just want to check for potential issues and cannot accept any system disruptions. This check is noninvasive and you can rerun it as necessary. You can expect the following output after you run the preliminary checks.
      All preliminary checks complete
      Finished running pre-checks.
    • Optional: Run the preliminary checks with --preliminary-check-with-fixes option:
      apupgrade --preliminary-check-with-fixes --upgrade-directory /localrepo --use-version 1.0.8.5_release --bundle system
      
      If you want to check for potential issues and attempt to automatically fix those. Run it if you can accept your system to be disrupted as this command might cause the nodes to reboot.
  7. Run:
    apupgrade --upgrade --upgrade-directory /localrepo --use-version 1.0.8.5_release --bundle system

Results

In 1.0.8.5, the Netezza web console runs on one of the three control nodes (or on a connector node if installed). There are two docker containers that are required for operation of the Netezza console: 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.

Procedure

  1. Run:
    /opt/ibm/appliance/platform/hpi/sys_hw_check node
    to verify the output. If it is showing PASS or ABOVE for all nodes, no action is required.
  2. If any of the nodes are showing BELOW, check the report log file to determine whether the nodes firmware must be upgraded or BMC settings updated.
  3. If any of the nodes report BELOW for firmware, run:
    /opt/ibm/appliance/platform/hpi/sys_hw_config -f -t target nodes
    for example:
    /opt/ibm/appliance/platform/hpi/sys_hw_config -f -t e1n{1..4}
  4. If any of the nodes only report incorrect BMC settings, run:
    /opt/ibm/appliance/platform/hpi/sys_hw_config -t target nodes
    for example:
    /opt/ibm/appliance/platform/hpi/sys_hw_config -t e1n{1..4}
  5. After you complete sys_hw_config and the nodes rebooted, run:
    /opt/ibm/appliance/platform/hpi/sys_hw_check node
    to confirm the updates took effect and the output is showing only PASS or ABOVE for all nodes.