Troubleshooting known issues

Pod "RESTARTS" count stays at 0 after a 4.5.x upgrade even though a few assistant pods are restarting

• Problem: After upgrading Watson Assistant, the pod "RESTARTS" count stays at 0 even though certain assistant pods are restarting.
• Cause: During the upgrade, custom resources owned by Watson Assistant for the "certificates.certmanager.k8s.io" CRD are deleted using a script that runs in the background. Sometimes the CR deletion script completes before the assistant operator gets upgraded. In that case, the old assistant operator might recreate custom resources for the "certificates.certmanager.k8s.io" CRD. Leftover CRs might cause the certificate manager to continuously regenerate some certificate secrets, causing some assistant pods to restart recursively.
• Solution: Run the following script to delete leftover custom resources for the "certificates.certmanager.k8s.io" CRD after setting INSTANCE (normally wa) and PROJECT_CPD_INSTANCE variables:

for i in `oc get certificates.certmanager.k8s.io -l icpdsupport/addOnId=assistant --namespace ${PROJECT_CPD_INSTANCE} | grep "${INSTANCE}-"| awk '{print $1}'`; do oc delete certificates.certmanager.k8s.io $i --namespace ${PROJECT_CPD_INSTANCE}; done

Data Governor not healthy after installation

After Watson Assistant is installed, the dataexhausttenant custom resource named wa-data-governor-ibm-data-governor-data-exhaust-internal gets stuck in the Topics phase. When this happens, errors in the Data Governor pods report that the service does not exist.

1. Get the status of the wa-data-governor custom resource:

   oc get DataExhaust
   

2. Wait for the wa-data-governor custom resource to be in the Completed phase:

   NAME               STATUS      VERSION   COMPLETED
   wa-data-governor   Completed   master    1s
   

3. Pause the reconciliation of the wa-data-governor custom resource:

   oc patch dataexhaust wa-data-governor -p '{"metadata":{"annotations":{"pause-reconciliation":"true"}}}' --type merge
   

4. Apply the fix to the dataexhausttenant custom resource:

   oc patch dataexhausttenant wa-data-governor-ibm-data-governor-data-exhaust-internal  -p '{"spec":{"topics":{"data":{"replicas": 1}}}}' --type merge
   

5. Wait for the Data Governor pods to stop failing. You can restart the admin pods to speed up this process.

6. Continue the reconciliation of the wa-data-governor custom resource:

   oc patch dataexhaust wa-data-governor --type=json -p='[{"op": "remove", "path": "/metadata/annotations/pause-reconciliation"}]'
   

RabbitMQ gets stuck in a loop after several installation attempts

After an initial installation or upgrade failure and repeated attempts to retry, the common services RabbitMQ operator pod can get into a CrashLoopBackOff state. For example, the log might include the following types of messages:

"error":"failed to upgrade release: post-upgrade hooks failed: warning:
Hook post-upgrade ibm-rabbitmq/templates/rabbitmq-backup-labeling-job.yaml
failed: jobs.batch "{%name}-ibm-rabbitmq-backup-label" already exists"

Resources for the ibm-rabbitmq-operator.v1.0.11 component must be removed before a new installation or upgrade is started. If too many attempts occur in succession, remaining resources can cause new installations to fail.

1. Delete the RabbitMQ backup label job from the previous installation or upgrade attempt. Look for the name of the job in the logs. The name ends in -ibm-rabbitmq-backup-label:

   oc delete job {%name}-ibm-rabbitmq-backup-label -n ${PROJECT_CPD_INSTANCE}
   

2. Check that the pod returns a Ready state:

   oc get pods -n ibm-common-services | grep ibm-rabbitmq
   

Preparing to install a size large Watson Assistant deployment

If you specify large for the watson_assistant_size option when you install Watson Assistant, the installation fails to complete successfully.

Before you install a size large deployment of Watson Assistant, apply the following fix. The following fix uses wa as the name of the Watson Assistant instance and cpd as the namespace where Watson Assistant is installed. These values are set in environment variables. Before you run the command, update the INSTANCE variable with the name of your instance, and update the NAMESPACE variable with the namespace where your instance in installed:

INSTANCE=wa ; \
NAMESPACE=cpd ; \
#DRY_RUN="--dry-run=client --output=yaml"     # To apply the changes, change to an empty string
DRY_RUN=""
cat <<EOF | tee wa-network-policy-base.yaml
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  annotations:
    oppy.ibm.com/internal-name: infra.networkpolicy
  labels:
    app: ${INSTANCE}-network-policy
    app.kubernetes.io/instance: ${INSTANCE}
    app.kubernetes.io/managed-by: Ansible
    app.kubernetes.io/name: watson-assistant
    component: network-policy
    icpdsupport/addOnId: assistant
    icpdsupport/app: ${INSTANCE}-network-policy
    icpdsupport/ignore-on-nd-backup: "true"
    icpdsupport/serviceInstanceId: inst-1
    service: conversation
    slot: ${INSTANCE}
    tenant: PRIVATE
    velero.io/exclude-from-backup: "true"
  name: ${INSTANCE}-network-policy
  namespace: ${NAMESPACE}
spec:
  ingress:
  - from:
    - podSelector:
        matchLabels:
          service: conversation
          slot: ${INSTANCE}
    - podSelector:
        matchLabels:
          slot: global
    - podSelector:
        matchLabels:
          component: watson-gateway
    - podSelector:
        matchLabels:
          component: dvt
    - podSelector:
        matchLabels:
          dwf_service: ${INSTANCE}-clu
          network-policy: allow-egress
    - podSelector:
        matchLabels:
          app: 0020-zen-base
    - namespaceSelector:
        matchLabels:
          ns: ${NAMESPACE}
      podSelector:
        matchLabels:
          app: 0020-zen-base
    - podSelector:
        matchLabels:
          component: ibm-nginx
    - namespaceSelector:
        matchLabels:
          ns: ${NAMESPACE}
      podSelector:
        matchLabels:
          component: ibm-nginx
    - namespaceSelector:
        matchLabels:
          assistant.watson.ibm.com/role: operator
      podSelector:
        matchLabels:
          release: assistant-operator
    - namespaceSelector:
        matchLabels:
          assistant.watson.ibm.com/role: operator
      podSelector:
        matchLabels:
          app: watson-assistant-operator
    - namespaceSelector:
        matchLabels:
          assistant.watson.ibm.com/role: operator
      podSelector:
        matchLabels:
          app.kubernetes.io/instance: watson-assistant-operator
    - namespaceSelector:
        matchLabels:
          assistant.watson.ibm.com/role: operator
      podSelector:
        matchLabels:
          app.kubernetes.io/instance: ibm-etcd-operator-release
    - namespaceSelector:
        matchLabels:
          assistant.watson.ibm.com/role: operator
      podSelector:
        matchLabels:
          app.kubernetes.io/instance: ibm-etcd-operator
  podSelector:
    matchLabels:
      service: conversation
      slot: ${INSTANCE}
  policyTypes:
  - Ingress
EOF
for MICROSERVICE in analytics clu-embedding clu-serving clu-training create-slot-job data-governor dialog dragonfly-clu-mm ed es-store etcd integrations master nlu recommends sireg-ubi-ja-tok-20160902 sireg-ubi-ko-tok-20181109 spellchecker-mm store store-admin store-cronjob store-sync store_db_creator store_db_schema_updater system-entities tfmm ui ${INSTANCE}-redis webhooks-connector
do
  # Change name and add component to selector
  # Apply to the cluster
  cat wa-network-policy-base.yaml | \
    oc patch --dry-run=client --output=yaml -f - --type=merge --patch "{
        \"metadata\": {\"name\": \"${INSTANCE}-network-policy-$( echo $MICROSERVICE | tr _ -)\"},
        \"spec\": {\"podSelector\":{\"matchLabels\":{\"component\": \"${MICROSERVICE}\"}}}
      }" |
    oc apply -f - ${DRY_RUN}
done

Fixing a size large Watson Assistant installation

Apply this fix if you installed a size large Watson Assistant deployment, and your installation fails to complete successfully. In some cases, Watson Assistant pods aren't able to communicate with other pods, and the Transmission Control Protocol (TCP) connections can't be established.

To confirm whether you are affected by this issue, run the following command:

oc logs --selector app=sdn --namespace openshift-sdn --container sdn | grep "Ignoring NetworkPolicy"

If you are affected, you see output similar to the following example:

W0624 12:58:21.407901    2480 networkpolicy.go:484] Ignoring NetworkPolicy cpd/wa-network-policy because it generates

If you encounter this error, apply the following fix to resolve the issue. The following fix uses wa as the name of the Watson Assistant instance. This value is set in an environment variable. Before you run the command, update the INSTANCE variable with the name of your instance:

INSTANCE=wa ; \
#DRY_RUN="--dry-run=client --output=yaml"     # To apply the changes, change to an empty string
DRY_RUN=""
for MICROSERVICE in analytics clu-embedding clu-serving clu-training create-slot-job data-governor dialog dragonfly-clu-mm ed es-store etcd integrations master nlu recommends sireg-ubi-ja-tok-20160902 sireg-ubi-ko-tok-20181109 spellchecker-mm store store-admin store-cronjob store-sync store_db_creator store_db_schema_updater system-entities tfmm ui ${INSTANCE}-redis webhooks-connector
do
  # Get original networking policy
  # Clean up metadata fields to get the resource applied by Watson Assistant
  # Change name and add component to selector
  # Apply to the cluster
  oc get networkpolicy $INSTANCE-network-policy --output yaml | \
  oc patch --dry-run=client --output=yaml -f - --type=json --patch='[
      {"op":"remove", "path":"/metadata/creationTimestamp"},
      {"op":"remove", "path":"/metadata/generation"},
      {"op":"remove", "path":"/metadata/resourceVersion"},
      {"op":"remove", "path":"/metadata/uid"},
      {"op":"remove", "path":"/metadata/annotations/kubectl.kubernetes.io~1last-applied-configuration"},
      {"op":"remove", "path":"/metadata/ownerReferences"}
    ]' | \
    oc patch --dry-run=client --output=yaml -f - --type=merge --patch "{
        \"metadata\": {\"name\": \"${INSTANCE}-network-policy-$( echo $MICROSERVICE | tr _ -)\"},
        \"spec\": {\"podSelector\":{\"matchLabels\":{\"component\": \"${MICROSERVICE}\"}}}
      }" |
    oc apply -f - ${DRY_RUN}
done

Unable to scale the size of Redis pods

When you scale the deployment size of Watson Assistant, the Redis pods do not scale correctly and will not match the new size of the Watson Assistant deployment (small, medium, or large). This problem is a known issue in Redis operator v1.5.1.

When you scale the size of your Watson Assistant deployment, you must delete the Redis custom resource. This allows Redis to automatically re-create the custom resource with the correct size and pods.

To delete and re-create the Redis custom resource:

1. Source the environment variables from the script:

   source ./cpd_vars.sh
   

   If you don't have the script that defines the environment variables, see Setting up installation environment variables.

2. Export the name of the Redis custom resource to an environment variable:

   export REDIS_CR_NAME=`oc get redissentinels.redis.databases.cloud.ibm.com -l icpdsupport/addOnId=assistant -n ${PROJECT_CPD_INSTANCE} | grep -v NAME| awk '{print $1}'`
   

3. Delete the Redis custom resource:

   oc delete redissentinels.redis.databases.cloud.ibm.com ${REDIS_CR_NAME} -n ${PROJECT_CPD_INSTANCE}
   

   It might take approximately 5 minutes for the custom resource to be re-created.

4. Verify that Redis is running:

   oc get redissentinels.redis.databases.cloud.ibm.com -n ${PROJECT_CPD_INSTANCE}
   

5. Export the name of your Watson Assistant instance as an environment variable:

   export INSTANCE=`oc get wa -n ${PROJECT_CPD_INSTANCE} |grep -v NAME| awk '{print $1}'`
   

6. Delete the Redis analytics secret:

   oc delete secrets ${INSTANCE}-analytics-redis
   

7. Delete the ${INSTANCE}-analytics deployment pods.

Data Governor error causing deployment failure

The following fix applies to Watson Assistant 4.0.0 through 4.0.8. In some cases, Watson Assistant deployment is stuck and pods are not coming up because of an issue with the interaction between the Events operator and the Data Governor custom resource (CR).

Complete the following steps to determine whether you are impacted by this issue and, if necessary, apply the patch to resolve it:

1. To determine whether you are impacted, run the following command to see whether the CR was applied successfully:

   oc get dataexhaust wa-data-governor -n $OPERAND_NS -o yaml
   

   If you do not receive any error, then you do not need to apply the patch. If you receive an error similar to the following example, complete the next step to apply the patch:

   message: 'Failed to create object: b''{"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"Internal
         error occurred: replace operation does not apply: doc is missing path: /metadata/labels/icpdsupport/serviceInstanceId:
         missing value","reason":"InternalError","details":{"causes":[{"message":"replace
         operation does not apply: doc is missing path: /metadata/labels/icpdsupport/serviceInstanceId:
         missing value"}]},"code":500}\n'''
       reason: Failed
       status: "True"
       type: Failure
     ibmDataGovernorService: InProgress
   

2. From your operand namespace, run the following command to apply the patch. In the command, wa is used as the name of the instance. Replace this value with the name of your Watson Assistant instance:

   cat <<EOF | oc apply -f -
   apiVersion: assistant.watson.ibm.com/v1
   kind: TemporaryPatch
   metadata:
     name: wa-data-governor
   spec:
       apiVersion: assistant.watson.ibm.com/v1
       kind: WatsonAssistant
       name: wa     # Replace wa with the name of your Watson Assistant instance
       patch:
         data-governor:
           dataexhaust:
             spec:
               additionalLabels:
                 icpdsupport/serviceInstanceId: inst-1
         kafkauser:
           metadata:
             labels:
               icpdsupport/serviceInstanceId: inst-1
   patchType: patchStrategicMerge
   EOF
   

   Wait about 15 minutes for the changes to take effect.

3. Validate that the patch was applied successfully:

   oc get dataexhaust wa-data-governor -n $OPERAND_NS -o yaml
   

   The patch was applied successfully when the value of serviceInstanceId is inst-1:

   spec:
     additionalLabels:
       icpdsupport/serviceInstanceId: inst-1
   

Security context constraint permission errors

The following fix applies to Watson Assistant 4.0.0 through 4.0.5. If a cluster has a security context constraint (SCC) that takes precedence over restricted SCCs and has different permissions than restricted SCCs, then Watson Assistant 4.0.0 through 4.0.5 installations might fail with permission errors. For example, the update-schema-store-db-job job reports errors similar to the following example:

oc logs wa-4.0.2-update-schema-store-db-job-bpsdr postgres-is-prepared
Waiting until postgres is running and responding
psql: error: could not read root certificate file "/tls/ca.crt": Permission denied
    - The basic command to postgres failed (retry in 5 sec)
psql: error: could not read root certificate file "/tls/ca.crt": Permission denied
    - The basic command to postgres failed (retry in 5 sec)
psql: error: could not read root certificate file "/tls/ca.crt": Permission denied
    - The basic command to postgres failed (retry in 5 sec)
..
..

Other pods might have similar permission errors. If you look at the SCCs of the pods, you can see they are not restricted. For example, if you run the oc describe pod wa-etcd-0 |grep scc command, you get an output similar to the following example:

openshift.io/scc: fsgroup-scc

To fix this issue, raise the priority of the restricted SCC so that it takes precedence. To do this, complete the following steps:

1. Run the following command:

   oc edit scc restricted
   

2. Change the priority from null to 1.

Now, new Watson Assistant pods default back to the expected restricted SCC. When you run the oc describe pod wa-etcd-0 |grep scc command, you get an output similar to the following example:

openshift.io/scc: restricted

Unable to collect logs with a webhook

The following fix applies to all versions of Watson Assistant 4.0.x. If you're unable to collect logs with a webhook, it might be because you are using a webhook that connects to a server that is using a self-signed certificate. If so, complete the following steps to import the certificate into the keystore so that you can collect Watson Assistant logs with a webhook:

1. Log in to cluster and oc project cpd-instance, which is the namespace where the Watson Assistant instance is located.

2. Run the following command. In the following command, replace INSTANCE_NAME with the name of your Watson Assistant instance and replace CUSTOM_CERTIFICATE with your Base64 encoded custom certificate key:

   INSTANCE="INSTANCE_NAME"     # Replace INSTANCE_NAME with the name of the Watson Assistant instance
   CERT="CUSTOM_CERTIFICATE"     # Replace CUSTOM_CERTIFICATE with the custom certificate key
   
   cat <<EOF | oc apply -f -
   apiVersion: v1
   data:
     ca_cert: ${CERT}
   kind: Secret
   metadata:
     name: ${INSTANCE}-custom-webhooks-cert
   type: Opaque
   ---
   apiVersion: assistant.watson.ibm.com/v1
   kind: TemporaryPatch
   metadata:
     name: ${INSTANCE}-add-custom-webhooks-cert
   spec:
     apiVersion: assistant.watson.ibm.com/v1
     kind: WatsonAssistantStore
     name: ${INSTANCE}
     patchType: patchStrategicMerge
     patch:
       webhooks-connector:
         deployment:
           spec:
             template:
               spec:
                 containers:
                 - name: webhooks-connector
                   env:
                   - name: CERTIFICATES_IMPORT_LIST
                     value: /etc/secrets/kafka/ca.pem:kafka_ca,/etc/secrets/custom/ca.pem:custom_ca
                   volumeMounts:
                   - mountPath: /etc/secrets/custom
                     name: custom-cert
                     readOnly: true
                 volumes:
                 - name: custom-cert
                   secret:
                     defaultMode: 420
                     items:
                     - key: ca_cert
                       path: ca.pem
                     secretName: ${INSTANCE}-custom-webhooks-cert
   EOF
   

3. Wait approximately 10 minutes for the wa-webhooks-connector pod to restart. This pod restarts automatically.

4. After the pod restarts, check the logs by running the following command. In the command, replace XXXX with the suffix of the wa-webhooks-connector pod:

   oc logs wa-webhooks-connector-XXXX     // Replace XXXX with the suffix of the wa-webhooks-connector pod
   

   After you run this command, you should see two lines similar to the following example at the beginning of the log:

   Certificate was added to keystore
   Certificate was added to keystore
   

   When you see these two lines, then the custom certificate was properly imported into the keystore.

Install Redis with Watson Assistant if foundational services version is higher than 3.14.1

If you are installing the Redis operator with Watson Assistant for IBM Cloud Pak® for Data 4.0.5 with an IBM Cloud Pak foundational services version higher than 3.14.1, the Redis operator might get stuck in Pending status. If you have an air-gapped cluster, complete the steps in the Air-gapped cluster section to resolve this issue. If you are using the IBM Entitled Registry, complete the steps in the IBM Entitled Registry section to resolve this issue.

Integrations image problem on air-gapped installations

If your Watson Assistant 4.0.4 installation is air-gapped, your integrations image fails to properly start.

If the installation uses the IBM Entitled Registry to pull images, complete the steps in the IBM Entitled Registry section. If the installation uses a private Docker registry to pull images, complete the steps in the Private Docker registry section.

Install Watson Assistant 4.0.0 with EDB version 1.8

Complete this task only if you need a fresh installation of Watson Assistant 4.0.0. Do not complete this task on existing clusters with data. Completing this task on an existing cluster with data results in data loss.

If you upgraded to EDB version 1.8 and need a new installation of Watson Assistant 4.0.0, complete the following steps. In the following steps, wa is used as the name of the custom resource. Replace this value with the name of your custom resource:

1. First, apply the following patch:

   cat <<EOF | oc apply -f -
   apiVersion: assistant.watson.ibm.com/v1
   kind: TemporaryPatch
   metadata:
     name: wa-postgres-180-hotfix
   spec:
     apiVersion: assistant.watson.ibm.com/v1
     kind: WatsonAssistantStore
     name: wa     # Specify the name of your custom resource
     patchType: patchStrategicMerge
     patch:
       postgres:
         postgres:
           spec:
             bootstrap:
               initdb:
                 options:
                  - "--encoding=UTF8"
                  - "--locale=en_US.UTF-8"
                  - "--auth-host=scram-sha-256"
   EOF
   

2. Run the following command to check that the temporary patch is applied to the WatsonAssistantStore custom resource. It might take up to 10 minutes after the store custom resource is updated:

   oc get WatsonAssistantStore wa -o jsonpath='{.metadata.annotations.oppy\.ibm\.com/temporary-patches}' ; echo
   

   If the patch is applied, the command returns output similar to the following example:

   {"wa-postgres-180-hotfix": {"timestamp": "2021-09-23T15:48:12.071497", "api_version": "assistant.watson.ibm.com/v1"}}`
   

3. Run the following command to delete the Postgres instance:

   oc delete clusters.postgresql.k8s.enterprisedb.io wa-postgres
   

4. Wait 10 minutes. Then, run the following command to check the Postgres instance:

   oc get pods | grep wa-postgres
   

   When the Postgres instance is running properly, the command returns output similar to the following example:

   wa-postgres-1                                                     1/1     Running     0          37m
   wa-postgres-2                                                     1/1     Running     0          36m
   wa-postgres-3                                                     1/1     Running     0          36m
   

5. Run the following command to check that the jobs that initialize the Postgres database completed successfully:

   oc get jobs wa-create-slot-store-db-job wa-4.0.0-update-schema-store-db-job
   

   When the jobs complete successfully, the command returns output similar to the following example:

   NAME                                  COMPLETIONS   DURATION   AGE
   wa-create-slot-store-db-job           1/1           3s         31m
   wa-4.0.0-update-schema-store-db-job   1/1           13s        31m
   

   If the jobs don't complete successfully, then they timed out and need to be recreated. Delete the jobs by running the oc delete jobs wa-create-slot-store-db-job wa-4.0.0-update-schema-store-db-job command. The jobs are recreated after 10 minutes by the Watson Assistant operator.

For information about upgrading from Watson Assistant 4.0.0 to Watson Assistant 4.0.2, see Upgrading Watson Assistant to a newer 4.0 refresh.

Search skill not working because of custom certificate

The search skill, which is the integration with the Watson Discovery service, might not work if you configured a custom TLS certificate in IBM Cloud Pak® for Data. If the custom certificate is not signed by a well-known certificate authority (CA), the search skill does not work as expected. You might also see errors in the Try out section of the search skill.

Disable Horizontal Pod Autoscaling and set a maximum number of master pods

Horizontal Pod Autoscaling (HPA) is enabled automatically for Watson Assistant. As a result, the number of replicas changes dynamically in the range of 1 to 10 replicas. You can disable HPA if you want to limit the maximum number of master pods or if you're concerned about master pods being created and deleted too frequently.

1. First, disable HPA for the master microservice by running the following command. In these steps, substitute your instance name for the INSTANCE_NAME variable:

   oc patch wa ${INSTANCE_NAME} --type='json' --patch='[{"op": "add", "path": "/appConfigOverrides/clu", "value":{"master":{"autoscaling":{"enabled":false}}}}]'
   

2. Wait until the information propagates into the Watson Assistant operator:

   sleep 600
   

3. Run the following command to remove HPA for the master microservice

   oc delete hpa ${INSTANCE_NAME}-master
   

4. Wait for about 30 seconds:

   sleep 30
   

5. Finally, scale down the master microservice to the number of replicas that you want. In the following example, the master microservice is scaled down to two replicas:

   oc scale deploy ${INSTANCE_NAME}-master --replicas=2
   

Watson Assistant 1.5.0 patch 1

Watson Assistant 1.5.0 patch 1 is available for installations of version 1.5.0.

Resizing the Redis statefulset memory and cpu values after applying patch 1 for Watson Assistant 1.5.0

Watson Assistant uses Redis to store web session-related data. Here are steps to resize Redis statefulset memory and cpu values after applying Watson Assistant 1.5.0 patch 1.

1. Use oc get wa to see your instance name:

   oc get wa
   NAME                       VERSION   READY   READYREASON   UPDATING   UPDATINGREASON   DEPLOYED   VERIFIED   AGE
   watson-assistant---wa-qa   1.5.0     True    Stable        False      Stable           18/18      18/18      11h
   

2. Export your instance name as a variable that you can use in each step, for example:

   export INSTANCENAME=watson-assistant---wa-qa
   

3. Change the updateStrategy in both Redis statefulsets to type RollingUpdate:

   oc patch statefulset c-$INSTANCENAME-redis-m -p '{"spec":{"updateStrategy":{"type":"RollingUpdate"}}}'
   oc patch statefulset c-$INSTANCENAME-redis-s -p '{"spec":{"updateStrategy":{"type":"RollingUpdate"}}}'
   

4. Update the Redis statefulsets with the resized cpu and memory values:

   Member CPU

   oc patch statefulset c-$INSTANCENAME-redis-m --type='json' -p='[{"op": "replace", "path": "/spec/template/spec/containers/0/resources/requests/cpu", "value":"50m"},{"op": "replace", "path": "/spec/template/spec/containers/1/resources/requests/cpu", "value":"50m"},{"op": "replace", "path": "/spec/template/spec/containers/2/resources/requests/cpu", "value":"50m"},{"op": "replace", "path": "/spec/template/spec/containers/3/resources/requests/cpu", "value":"50m"}]'
   

   Member memory

   oc patch statefulset c-$INSTANCENAME-redis-m --type='json' -p='[{"op": "replace", "path": "/spec/template/spec/containers/0/resources/limits/memory", "value":"256Mi"},{"op": "replace", "path": "/spec/template/spec/containers/1/resources/limits/memory", "value":"256Mi"},{"op": "replace", "path": "/spec/template/spec/containers/2/resources/limits/memory", "value":"256Mi"},{"op": "replace", "path": "/spec/template/spec/containers/3/resources/limits/memory", "value":"256Mi"},{"op": "replace", "path": "/spec/template/spec/containers/0/resources/requests/memory", "value":"256Mi"},{"op": "replace", "path": "/spec/template/spec/containers/1/resources/requests/memory", "value":"256Mi"},{"op": "replace", "path": "/spec/template/spec/containers/2/resources/requests/memory", "value":"256Mi"},{"op": "replace", "path": "/spec/template/spec/containers/3/resources/requests/memory", "value":"256Mi"}]'
   

   Sentinel CPU

   oc patch statefulset c-$INSTANCENAME-redis-s --type='json' -p='[{"op": "replace", "path": "/spec/template/spec/containers/0/resources/requests/cpu", "value":"50m"},{"op": "replace", "path": "/spec/template/spec/containers/1/resources/requests/cpu", "value":"50m"},{"op": "replace", "path": "/spec/template/spec/containers/2/resources/requests/cpu", "value":"50m"},{"op": "replace", "path": "/spec/template/spec/containers/3/resources/requests/cpu", "value":"50m"}]'
   

   Sentinel memory

   oc patch statefulset c-$INSTANCENAME-redis-s --type='json' -p='[{"op": "replace", "path": "/spec/template/spec/containers/0/resources/limits/memory", "value":"256Mi"},{"op": "replace", "path": "/spec/template/spec/containers/1/resources/limits/memory", "value":"256Mi"},{"op": "replace", "path": "/spec/template/spec/containers/2/resources/limits/memory", "value":"256Mi"},{"op": "replace", "path": "/spec/template/spec/containers/3/resources/limits/memory", "value":"256Mi"},{"op": "replace", "path": "/spec/template/spec/containers/0/resources/requests/memory", "value":"256Mi"},{"op": "replace", "path": "/spec/template/spec/containers/1/resources/requests/memory", "value":"256Mi"},{"op": "replace", "path": "/spec/template/spec/containers/2/resources/requests/memory", "value":"256Mi"},{"op": "replace", "path": "/spec/template/spec/containers/3/resources/requests/memory", "value":"256Mi"}]'
   

5. Confirm the Redis member and sentinel pods have the new memory and cpu values, for example:

   oc describe pod c-$INSTANCENAME-redis-m-0 |grep cpu

   oc describe pod c-$INSTANCENAME-redis-m-0 |grep memory

   oc describe pod c-$INSTANCENAME-redis-s-0 |grep cpu

   oc describe pod c-$INSTANCENAME-redis-s-0 |grep memory

   The results should look like these examples:

   oc describe sts c-$INSTANCENAME-redis-m |grep cpu
                         {"m":{"db":{"limits":{"cpu":"4","memory":"256Mi"},"requests":{"cpu":"25m","memory":"256Mi"}},"mgmt":{"limits":{"cpu":"2","memory":"100Mi"}...
         cpu:     4
         cpu:     50m
         cpu:     2
         cpu:     50m
         cpu:     2
         cpu:      50m
         cpu:     2
         cpu:     50m
   

   oc describe sts c-$INSTANCENAME-redis-m |grep memory
                         {"m":{"db":{"limits":{"cpu":"4","memory":"256Mi"},"requests":{"cpu":"25m","memory":"256Mi"}},"mgmt":{"limits":{"cpu":"2","memory":"100Mi"}...
         memory:  256Mi
         memory:  256Mi
         memory:  256Mi
         memory:  256Mi
         memory:  256Mi
         memory:   256Mi
         memory:  256Mi
         memory:  256Mi
   

   oc describe pod c-$INSTANCENAME-redis-s-0 |grep cpu
                   {"m":{"db":{"limits":{"cpu":"4","memory":"256Mi"},"requests":{"cpu":"25m","memory":"256Mi"}},"mgmt":{"limits":{"cpu":"2","memory":"100Mi"}...
         cpu:     2
         cpu:     50m
         cpu:     2
         cpu:     50m
         cpu:     2
         cpu:      50m
         cpu:     2
         cpu:     50m
   

   oc describe pod c-$INSTANCENAME-redis-s-0 |grep memory
                   {"m":{"db":{"limits":{"cpu":"4","memory":"256Mi"},"requests":{"cpu":"25m","memory":"256Mi"}},"mgmt":{"limits":{"cpu":"2","memory":"100Mi"}...
         memory:  256Mi
         memory:  256Mi
         memory:  256Mi
         memory:  256Mi
         memory:  256Mi
         memory:   256Mi
         memory:  256Mi
         memory:  256Mi
   

6. Change the updateStrategy in both Redis statefulsets back to type OnDelete:

   oc patch statefulset c-$INSTANCENAME-redis-m -p '{"spec":{"updateStrategy":{"type":"OnDelete"}}}'
   oc patch statefulset c-$INSTANCENAME-redis-s -p '{"spec":{"updateStrategy":{"type":"OnDelete"}}}'
   

Delete the pdb (poddisruptionbudgets) when changing instance from medium to small

Whenever the size of Watson Assistant is changed from medium to small, a manual step is required to delete the poddisruptionbudgets that are created for medium instances.

Run the following command, replacing <instance-name> with the name of your Watson Assistant CR instance and replacing <namespace-name> with the name of the namespace where the instance resides.

oc delete pdb  -l icpdsupport/addOnId=assistant,component!=etcd,ibmevents.ibm.com/kind!=Kafka,app.kubernetes.io/instance=<instance-name> -n <namespace-name>