IBM Support

IBM Automation Decision Services 23.0.x known limitations

Release Notes


Abstract

This web page provides a list of known limitations in Automation Decision Services 23.0.x. Workarounds are provided where possible.

Content

IBM Automation Decision Services 23.0.2
The following limitations pertain to IBM Automation Decision Services 23.0.2. They are subject to change between releases. You can find more limitations in the product documentation at IBM Automation Decision Services 23.0.2: Known limitations.
Issue Description Version

Incorrect download path for engine-compact-runtime-3.1.9.jar
Symptom:

The engine-compact-runtime-3.1.9.jar file is currently unavailable for downloading due to a typographical error in its download path.

The engine-compact-runtime-3.1.9.jar redirects to 'engine-compact-runtime/3.1.9/engine-compact-runtime-3.1.6.jar'

Solution:

Manually set the desired version for engine-compact-runtime-<version>.jar in the download path.

For example: engine-compact-runtime/3.1.9/engine-compact-runtime-3.1.9.jar

 23.0.2
IBM Automation Decision Services 23.0.1
The following limitations pertain to IBM Automation Decision Services 23.0.1. They are subject to change between releases. You can find more limitations in the product documentation at IBM Automation Decision Services 23.0.1: Known limitations.
Issue Description Version

The installation might be interrupted while the installation script is running in an environment other than OpenShift Container Platform (OCP).

Symptom:

The installation of Automation Decision Services might be interrupted while the installation script (ads-install.sh) is running in an environment other than OpenShift Container Platform (OCP); for example, Amazon Elastic Kubernetes Service (EKS).

The EDB operator that comes as an Automation Decision Services transitive dependency does not start out of the box.

Cause:

There are issues in the current foundational services.

Solution:

After you apply the Automation Decision Services custom resources (CR), wait for the EDB csv "Failed" status, for example:

# kubectl get csv -n <ads-namespace> | grep EDB
NAME                                          DISPLAY                                VERSION   REPLACES                          PHASE
cloud-native-postgresql.v1.18.4               EDB Postgres for Kubernetes            1.18.4    cloud-native-postgresql.v1.18.3   Failed

Then, run the following command:

namespace=<ads-namespace>
edb_csv=$(kubectl -n ${namespace} get csv -l operators.coreos.com/cloud-native-postgresql.${namespace}="" -o name)

kubectl -n ${namespace} patch $edb_csv  --type=json -p '[{"op":"add","path":"/spec/install/spec/deployments/0/spec/template/spec/securityContext/runAsUser","value":1001}]'

edb_deployment=$(kubectl -n ${namespace} get deployment -l operators.coreos.com/cloud-native-postgresql.${namespace}="" -o name)

kubectl -n ${namespace} patch $edb_deployment  --type=json -p '[{"op":"add","path":"/spec/template/spec/securityContext/runAsUser","value":1001}]'

As a result, the EDB operator starts, and the Automation Decision Services CR reconciliation can continue.

For more information about issues in the foundational services, see Known issues in foundational services in the foundational services documentation.

 23.0.1

The installation might be interrupted while the installation script is running in an environment other than OpenShift Container Platform (OCP).

Symptom:

The installation of Automation Decision Services might be interrupted while the installation script (ads-install.sh) is running in an environment other than OpenShift Container Platform (OCP); for example, Amazon Elastic Kubernetes Service (EKS).

On Amazon Elastic Kubernetes Service (EKS), the EBS storage class (default block storage class) does not work out of the box for Platform UI (Zen) installation that is triggered by Automation Decision Services reconciliation. 

Cause:

There are issues in the current foundational services.

Solution:

After you apply the Automation Decision Services custom resource (CR), wait for zen-minio-0 pod CrashLoopBackoff status to apply a command to fix its parent StatefulSet:

namespace=<ads-namespace>
kubectl -n ${namespace} patch sts/zen-minio  --type=json -p '[{"op":"add","path":"/spec/template/spec/securityContext/fsGroup","value":0}]'
For more information about issues in the foundational services, see Known issues in foundational services in the foundational services documentation.
 23.0.1
The installation of more than one instance on a non-OpenShift cluster fails.
Symptom:
Trying to install more than one instance of Automation Decision Services on the same non-OpenShift cluster fails.
Cause:
Each instance tries to use the same ingress URL.
Solution:
  1. In the ibmcloud-cluster-info configmap, manually replace the cluster_adress value with cp-console-ads.<domain_name>.
  2. Rerun the iam-config-job job: 
    ​kubectl get job iam-config-job -o json | jq 'del(.spec.selector)' | jq 'del(.spec.template.metadata.labels)' | kubectl replace --force -f
  3. Update the ingresses as follows: 
    kubectl get ingress
NAME                         CLASS    HOSTS                                             ADDRESS                                                                     PORTS   AGE
cncf-common-web-ui           <none>   cp-console-ads.<domain_name>                      10.21.66.152,10.21.66.173,10.21.66.243,10.21.67.11,10.21.67.66,9.46.83.81   80      4d7h
cncf-id-mgmt                 <none>   cp-console-ads.<domain_name>                      10.21.66.152,10.21.66.173,10.21.66.243,10.21.67.11,10.21.67.66,9.46.83.81   80      4d7h
cncf-platform-auth           <none>   cp-console-ads.<domain_name>                      10.21.66.152,10.21.66.173,10.21.66.243,10.21.67.11,10.21.67.66,9.46.83.81   80      4d7h
cncf-platform-id-auth        <none>   cp-console-ads.<domain_name>                      10.21.66.152,10.21.66.173,10.21.66.243,10.21.67.11,10.21.67.66,9.46.83.81   80      4d7h
cncf-platform-id-provider    <none>   cp-console-ads.<domain_name>                      10.21.66.152,10.21.66.173,10.21.66.243,10.21.67.11,10.21.67.66,9.46.83.81   80      4d7h
cncf-platform-login          <none>   cp-console-ads.<domain_name>                      10.21.66.152,10.21.66.173,10.21.66.243,10.21.67.11,10.21.67.66,9.46.83.81   80      4d7h
cncf-platform-oidc           <none>   cp-console-ads.<domain_name>                      10.21.66.152,10.21.66.173,10.21.66.243,10.21.67.11,10.21.67.66,9.46.83.81   80      4d7h
cncf-saml-ui-callback        <none>   cp-console-ads.<domain_name>                      10.21.66.152,10.21.66.173,10.21.66.243,10.21.67.11,10.21.67.66,9.46.83.81   80      4d7h
cncf-social-login-callback   <none>   cp-console-ads.<domain_name>                      10.21.66.152,10.21.66.173,10.21.66.243,10.21.67.11,10.21.67.66,9.46.83.81   80      4d7h
zen-ingress                  <none>   ads-cpd.<domain_name>                             10.21.66.152,10.21.66.173,10.21.66.243,10.21.67.11,10.21.67.66,9.46.83.81   80      4d8h
 23.0.1
Monitoring executions with the IBM License Metric Tool fails.
Symptom:
The decision usage monitoring does not work with the execution Java API.
Cause:
The IBM License Metric tool cannot find the swidtag file ibm.com_IBM_Automation_Decision_Services.swidtag.
Solution:
Rename the swidtag file to ibm.com_IBM_Automation_Decision_Services-22.0.2.swidtag and add it to the application classpath.
 23.0.1

[{"Type":"MASTER","Line of Business":{"code":"LOB76","label":"Data Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSD1E4E","label":"IBM Automation Decision Services"},"ARM Category":[{"code":"a8m3p000000hCCwAAM","label":"ADS standalone"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"23.0.1;23.0.2"}]

Document Information

Modified date:
14 March 2025

UID

ibm17001307

Page Feedback