Cannot connect to Redis
Db2® Data Management Console fails to connect to Redis server.
Symptoms
Redis cannot connect to Db2 Data Management Console.Causes
The issue is cause due to a known issue on s390x architecture for Redis 1.6.3.
Resolving the problem
To resolve the problem, upgrade Redis from 1.6.3 to 1.6.4.
- Delete the Db2 Data Management Console CR, Redis CSV, and
subscription.
oc project <project-namespace> oc delete dmc data-management-console oc delete csv ibm-cloud-databases-redis.v1.6.3 -n ibm-common-services oc delete sub redis-operator -n ibm-common-services
- Edit the Redis operator catalog
source.
oc edit catalogsource ibm-cloud-databases-redis-operator-catalog -n openshift-marketplace -o yaml, replace image to icr.io/cpopen/ibm-cloud-databases-redis-catalog@sha256:708f4ba1545b2c7476165064f28b0c481b2a3077ef2208f3d24fd02941f9d6d0
- Provision a new Db2 Data Management Console
instance.
cat << EOF | oc apply -f - apiVersion: dmc.databases.ibm.com/v1 kind: Dmc metadata: annotations: ansible.operator-sdk/reconcile-period: 30s ansible.sdk.operatorframework.io/verbosity: "4" name: data-management-console namespace: <project-namespace> spec: description: IBM Db2 Data Management Console license: accept: true license: Standard scaleConfig: small storageClass: nfs-client storageSize: 10Gi total_resources: limits: cpu: "" memory: "" version: 4.6.2 EOF
- Verify whether Redis CSV is updated to version
1.6.4.
# oc get csv -n ibm-common-services NAME DISPLAY VERSION REPLACES PHASE ibm-cloud-databases-redis.v1.6.4 IBM Operator for Redis 1.6.4 ibm-cloud-databases-redis.v1.6.3 Succeeded ibm-common-service-operator.v3.23.0 IBM Cloud Pak foundational services 3.23.0 Succeeded ...
- Wait for a few minutes. Verify whether the Redis pods are started.