IBM Support

CP4S Data Sources page blank

Troubleshooting


Problem

A blank Data Sources page in IBM Cloud Pak for Security prevents users from viewing, adding, or managing data sources, effectively blocking the onboarding and operation of integrations within the platform.

Symptom

  • The Data Sources UI does not load any content.
  • No visible error message is displayed in the UI.
  • One or more udi-udiworker pods are not in a healthy state.

Cause

The issue occurs when one or more udi-udiworker pods fail to initialize correctly or enter a crash loop. Since these pods are responsible for populating and managing data source metadata, their failure causes the CP4S Data Sources UI to load as blank

Environment

  • Product: IBM Cloud Pak for Security (CP4S)
  • Component: Universal Data Ingestion (UDI)
  • Platform: Red Hat OpenShift

Diagnosing The Problem

Verify UDI worker pod status

Run the following command and check the status of udi-udiworker pod

oc get pods | grep udi-udiworker

One or more pods may be in the following states:

  • Init
  • CrashLoopBackOff
  • 0/1 Ready

Check logs for UDI worker pods

Review the logs to confirm initialization or connectivity issues:

oc logs -l name=udi-udiworkers

If logs repeatedly show messages such as:

  • Reconnecting to rabbit
  • RabbitMQ connection failures

This indicates a backend messaging dependency issue affecting UDI initialization.

 

Resolving The Problem

  1. Restart the UDI worker pods
     Delete the affected pods so OpenShift can recreate them:
    oc delete pod -l name=udi-udiworker
  2. Verify pod health
    Ensure all udi-udiworker pods return to a healthy state:
    oc get pods | grep udi-udiworker
  3. All pods should be in Running state with 1/1 Ready status.
  4. Validate the Data Sources page
    • Log in to the CP4S user interface.
    • Navigate to Data Sources.
    • Confirm that data sources are visible and can be added or managed.

Additional Information:

  • If the UDI worker logs continue to display “reconnecting to rabbit”, follow the RabbitMQ recovery and troubleshooting steps outlined in the following documentation:
    Refer to: https://www.ibm.com/docs/en/cloud-paks/cp-security/1.10.0?topic=troubleshooting-rabbitmq-pods-crash-after-installing-upgrading
  • Ensure RabbitMQ services and related dependencies are operational before restarting UDI pods.

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSTDPP","label":"IBM Cloud Pak for Security"},"ARM Category":[{"code":"a8m3p000000F8z2AAC","label":"Cloud Pak for Security (CP4S)-\u003EAPI"}],"ARM Case Number":"TS021908107","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"1.1.0;1.10.0;1.11.0;1.2.0;1.3.0;1.4.0;1.5.0;1.6.0;1.7.0;1.7.1;1.7.2;1.8.0;1.9.0"}]

Document Information

Modified date:
12 May 2026

UID

ibm17271524

Page Feedback