Known issues and limitations

Known issues and limitations in the IBM® Cloud Pak System user interface.

  • If you log into the IBM Cloud Pak System user interface when deployment services are down, you might encounter delays with loading of menus and pages. If this issue still persists, refresh the page or logout and login again.
  • Entering an incorrect time format for Start on and Run until in the Configure deployment tab of the IBM Cloud Pak System user interface indicates an error message and the system time is considered during deployment. For more information, see Start on and Run until values.
  • For Cloud Paks deployment, if you deploy from the Provision accelerators page of the user interface, then the deployment does not support Patten Deployer type of Environment profile. In such a case, deploy specific accelerator by using the traditional way of deployment.
  • Following are the default accelerator names that are included with Version 2.3.4 release:
    Cloud Pak For Applications: CP4 Applications on OCP4 - HA
Cloud Pak For Automation: CP4 Automation on OCP4 - HA
Cloud Pak For Integration: CP4 Integration on OCP4 - HA
Cloud Pak for Integration with OCS: CP4 Integration on OCP4 - HA with OCS
Cloud Pak for Multi-Cloud Management: CP4 Multicloud Management on OCP4 - HA
Cloud Pak For Security: CP4 Security on OCP4 - HA
IBM Edge Application Manager: IBM Edge Application Manager - HA
OpenShift Container Platform: OpenShift Container Platform 4 - HA
Openshift Container Platform with OCS: OpenShift Container Platform 4 HA with OCS

    You can clone a accelerator name with a different name from the System management user interface and set it as the default accelerator. However, the mapping file in the IBM Cloud Pak System user interface might still point to the older accelerator name. If your system does not have accelerators with those names, then the console displays the Installation file missing message in the catalog for that accelerator in IBM Cloud Pak.

    Use API to manually update the mapping file. It includes your accelerator name as the default accelerator. For more information about the API, see Modifying mapping.json REST API.

  • Browser issues:
    • If you close the browser tabs of both System management user interface and IBM Cloud Pak System user interface without logging out, then the next IBM Cloud Pak System log in attempt in the same browser session takes you directly to the System management user interface with the previously logged-in user credentials.
    • If you log out from the System management user interface, then the refresh of IBM Cloud Pak System user interface tab must render the log in page by default. It is a known issue that the session time-out happens only after you click anywhere within the IBM Cloud Pak System user interface.
    • Sometimes, when a session expires, the URL address gets malformed and "Not found" error occurs. To resolve this issue, click Go Home to open the right page.

For IBM Cloud Pak System accelerators known issues and limitations, see the specific section in Known issues and limitations.

For troubleshooting information about the System management user interface, see Troubleshooting and support.