Upgrading Cloud Pak for Data System to version

Cloud Pak for Data System version is a hotfix that only updates the platform management component. When upgrading, you only have to upgrade the system bundle. You must be on version to upgrade to version

Before you begin

  1. Depending on your environment:
    • If the system already has a custom network configuration, it must be configured via the /opt/ibm/appliance/platform/apos-comms/customer_network_config/ansible with a System_Name.yml file (see point 2).
    • If apupgrade detects custom network configuration and no yml file, it will fail at a precheck.
    • If you are upgrading a new system with no network configuration, the apupgrade will not stop at the check for System_Name.yml, but will continue the upgrade process.
  2. If your system has custom network configuration:

    Before you upgrade, ensure that in /opt/ibm/appliance/platform/apos-comms/customer_network_config/ansible there is a System_Name.yml file specifying the house network configuration.

    To locate the file, run the following command:
    ls -t *yml | grep -v template | head -1

    If the file does not exist, you have to create it. Otherwise your network configuration might be lost during the upgrade. For more information on the file and how to create it for versions older than, see the Node side network configuration section, and the following link specifically: Editing the network configuration YAML file.

About this task

If any part of the upgrade fails, contact IBM Support for instructions on how to clean up and proceed. The disk space is tightly managed, and not all items are present at all times. When re-running an upgrade due to encountered issues, low space can be an issue.


  1. Connect to node e1n1 via the management address and not the application address or floating address.
  2. On node e1n1, create a /localrepo/ directory (including parent if necessary).
    Note: The name of the directory that you use must be unique. You cannot use a folder name that you already used.
    mkdir /localrepo/
  3. Download the ICPDS system bundle from Fix Central.
  4. Move the bundle files into the /localrepo/ directory.
  5. If you had to extract the network templates as specified in the prerequisite steps, run the following command:
    rm -rf /localrepo/
  6. Upgrade the apupgrade script:
    apupgrade --upgrade-apupgrade --upgrade-directory /localrepo --use-version --bundle system
  7. Optional: Run upgrade details to view details about the specific upgrade version:
    apupgrade --upgrade-details --upgrade-directory /localrepo --use-version --bundle system
  8. Run preliminary checks before starting the upgrade:
    apupgrade --preliminary-check --upgrade-directory /localrepo --use-version --bundle system
  9. Initiate the upgrade of the system servers by running:
    apupgrade --upgrade --upgrade-directory /localrepo --use-version --bundle system

    The value for the --use-version parameter is the same as the name of the directory you created in Step 1.

  10. Run rm -rf /localrepo/*. The command enables you to rerun the apupgrade command if you wish to do so.
  11. After the system is successfully upgraded, you need to apply the following workaround steps to avoid the known issue with Cloud Pak for Data pods endpoints not being created:
    1. Ensure that the system is up and in Ready state, and log in to the control VM:
      ssh e1n1-1-control
    2. Edit node configuration. The configuration is opened in VI editor:
      $ oc edit cm node-config-compute-crio -n openshift-node
    3. Add the following lines in the kubeletArguments section, with proper indentation:
        - "cpu=250m,memory=512Mi"
        - "cpu=250m,memory=512Mi"
    4. Save and quit.

What to do next

If you have Netezza® Performance Server on your system: Upgrading Cloud Pak for Data System does not upgrade the Netezza Performance Server software. The Netezza Performance Server releases are independent of the Cloud Pak for Data System releases. Whenever a new version is available on Fix Central, you can upgrade it as described in Upgrading IBM Performance Server.