Known issues for IBM StreamSets

Known issues

Login audit displays incorrect IP address

Applies to: 5.1.0 and later

The login audit incorrectly displays the IP address of the Red Hat® OpenShift® Container Platform cluster rather than the IP address of the workstation where the user logged in.

Cannot install IBM StreamSets with deprecated LDAP integration

Applies to: 5.1.0 and later

IBM StreamSets installation fails when IBM Software Hub uses the deprecated LDAP integration that is provided by IBM Software Hub.

IBM StreamSets requires IBM Software Hub to use the LDAP integration provided by the Identity Management Service in IBM Cloud Pak foundational services.

Workaround: Enable the Identity Management Service in IBM Software Hub.
For details, see Integrating with the Identity Management Service.

An IBM StreamSets upgrade remains in an In Progress state when a ResourceQuota is applied to the operand namespace

Applies to: 5.1.0 and later

Fixed in: 5.2.2

When you upgrade IBM StreamSets from Version 5.1.x to Version 5.2.x or from Version 5.2.x to a later 5.2 refresh, the IBM StreamSets service remains in an In Progress state when a ResourceQuota is applied to the operand namespace.

Workaround: Apply a limit range to the operand namespace with defaults for limits and requests. For example, you can apply the limit range as shown in the following yaml:

apiVersion: v1
kind: LimitRange
metadata:
  name: cpd-limitrange
  namespace: ${PROJECT_CPD_INST_OPERANDS}
spec:
  limits:
  - type: Container
    default:
      cpu: "500m"
      memory: "256Mi"
    defaultRequest:
      cpu: "100m"
      memory: "64Mi"

Then check the progress of the upgrade:

oc describe StreamSetsInstaller streamsets  -n ${PROJECT_CPD_INST_OPERANDS}

If the upgrade is not progressing, restart the IBM StreamSets operator pod:

oc delete $(oc get pods -n ${PROJECT_CPD_INST_OPERATORS} -l icpdsupport/addOnId=streamsets -o name) -n ${PROJECT_CPD_INST_OPERATORS}