Upgrading

Use these solutions to help resolve problems that you might encounter with upgrading IBM® Cloud Pak for Network Automation.

Multitenancy-related menu items do not appear after an upgrade

Symptom

If you upgrade and enable multitenancy, menu items that relate to multitenancy might not appear in the IBM Cloud Pak® console.

For example, the Network Automation Tenant Admin role might not appear in the list of roles when a user clicks Profile and settings from the profile menu.

Cause

The zen-watcher service needs to be restarted.

Solution

Delete the zen-watcher pod to restart the service.

Site Planner information and UI cannot be accessed after upgrade to 2.6.0

Symptom

If you upgrade from 2.5.0 to 2.6.0, you might not be able to view Site Planner information or access the Site Planner UI.

On the home page for the network automation UI, you might see the following message in the Infrastructure components panel:
The data cannot be displayed.
If you click View details, the following message is shown:
HTTP 403 Forbidden
Also, if you select any of the Site Planner menu items from the navigation menu Navigation menu icon, you are redirected to the network automation UI home page.
Cause

An authentication setting is missing from the Site Planner configuration secret.

Solution
To work around this problem, update the cp4na-o-siteplanner-configuration secret by completing the following steps:
  1. Log in to your OpenShift® Container Platform cluster console.
  2. From the navigation menu, click Workloads > Secrets.
  3. Search for the cp4na-o-siteplanner-configuration secret.
  4. Click cp4na-o-siteplanner-configuration to open the secret details page.
  5. From the Actions list, click Edit Secret.
  6. Append the following secret to the configuration.yaml key value: 
    TOKEN_EXCHANGE_URL: "https://cp4na-o-ishtar:8280/api/v1/token"
  7. Click Save.
  8. Log out of your IBM Cloud Pak console.
  9. Find the name of the Site Planner pod by running the following command: 
    oc get pods | grep cp4na-o-siteplanner
  10. Restart the Site Planner pod by running the following command: 
    oc delete pod <siteplanner_pod>

    where <siteplanner_pod> is the pod name that you got in the previous step.

    Wait until the pod is restarted. The command might take a few minutes to complete.

  11. Log in to your IBM Cloud Pak console and verify that you can view the Site Planner information and access the Site Planner UI.