Impact fails to integrate with IBM Tivoli Directory Server on NOI OCP

Troubleshooting

Problem

NOI on OpenShift Container Platform is configured to integrate with IBM Tivoli Directory Server LDAP.

The value 'ServerType: IDS' is set in the noi-operator yaml and the webgui pod starts correctly, however Impact does not.

Symptom

The following messages are in the nciserver log:

Waiting for Impact to be fully functional
nci_trigger: Failed to trigger policy [UTIL] (error 1)
.The Impact process pid is 2867
nci_trigger: Failed to trigger policy [UTIL] (error 1)
.The Impact process pid is 2867
nci_trigger: Failed to trigger policy [UTIL] (error 1)
.The Impact process pid is 2867
nci_trigger: Failed to trigger policy [UTIL] (error 1)
.The Impact process pid is 2867
nci_trigger: Failed to trigger policy [UTIL] (error 1)
.The Impact process pid is 2867
nci_trigger: Failed to trigger policy [UTIL] (error 1)
.ERROR The Impact process is not actually running at all. Let the pod restart.
ERROR
Failed to detect a functional Impact server, restarting impact

Cause

The LDAP_SERVERTYPE parameter in both the nciserver and impactgui pods needs to be changed.

Environment

NOI on OpenShift Container Platform.

Resolving The Problem

You need to edit the statefulsets for both the nciserver and impactgui.

This change can be made either in the GUI or on the command line.

Proceed as follows on the command line:

1) Back up the statefulsets:

oc get sts [deployment-name]-impactgui -o yaml > impact.yaml

oc get sts [deployment-name]-nciserver -o yaml > nciserver.yaml

2) Edit the first statefulset for example,

oc edit sts [deployment-name]-impactgui

3) Make the following changes:

Under the section for labels, add the following entry:

managedByUser: "true"

(Note and follow the indentation for the section)

Change the value for LDAP_SERVERTYPE from IDS to "IBM Tivoli Directory Server"

4) Do the same for the other statefulset, for example

oc edit sts [deployment-name]-nciserver

5) Delete both pods so they restart with the new values.

The statefulsets retain the new values on restart, due to the 'managedByUser: "true"' setting.

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSE9G0Q","label":"IBM Cloud Pak for AIOps"},"ARM Category":[{"code":"a8m0z0000000CfqAAE","label":"Watson AIOps-\u003EEvent Manager \/ NOI-\u003EImpact-\u003ESecurity-\u003ELDAP User Repository-\u003EUser repository"}],"ARM Case Number":"TS014896606","Platform":[{"code":"PF016","label":"Linux"}],"Version":"All Versions"}]

Historical Number

TS014896606

Was this topic helpful?

Document Information

Modified date:
05 December 2023

UID

ibm17090402

Tips