CP4S: Check the configuration of your data sources or get support within the IBM Support Portal.

Resolving The Problem

1.  Rebuild minio CRD.
   1. List minio CRD:

      oc get minio
      NAME       AGE
      ow-minio   4h10m
      

   2. Back up a copy of minio CRD:

      oc get minio ow-minio -o yaml > minio.yaml

   3. Confirm the minio.yaml file was saved successfully:

      less minio.yaml
      
      sample:
      
      apiVersion: isc.ibm.com/v1
      kind: Minio
      metadata:
        creationTimestamp: "2021-12-29T00:17:36Z"
        finalizers:
        - isc.ibm.com/finalizer
        generation: 15
        labels:
          app: dataservices
          app.kubernetes.io/instance: default
          app.kubernetes.io/managed-by: cp4s-operator
          app.kubernetes.io/name: dataservices
          chart: dataservices
          instance: ow-minio
          release: dataservices
          sort: minio
        managedFields:
        - apiVersion: isc.ibm.com/v1
          fieldsType: FieldsV1
          fieldsV1:
            f:metadata:
              f:labels:
                f:app: {}
                f:app.kubernetes.io/instance: {}
                f:app.kubernetes.io/managed-by: {}
                f:app.kubernetes.io/name: {}
                f:chart: {}
                f:instance: {}
                f:release: {}
                f:sort: {}
            f:spec:
              f:cluster_domain: {}
              f:cpu_limit: {}
              f:cpu_request: {}
              f:default_bucket_enabled: {}
              f:memory_limit: {}
              f:memory_request: {}
              f:minio_port: {}
              f:persistence_enabled: {}
              f:replicas: {}
              f:storage_access_mode: {}
              f:storage_class: {}
              f:storage_dynamic_provisioning: {}
              f:storage_size: {}
              f:storage_sub_path: {}
              f:tls_enabled: {}
              f:uuid: {}
          manager: cp4s-operator
          operation: Apply
          time: "2023-01-25T12:07:29Z"
        - apiVersion: isc.ibm.com/v1
          fieldsType: FieldsV1
          fieldsV1:
            f:metadata:

   4. Delete minio CRD:

      oc delete minio ow-minio
      minio.isc.ibm.com "ow-minio" deleted

   5. Delete all minio Persistent Volume Claims: 

      kubectl delete pvc export-ibm-minio-ow-minio-ibm-minio-0
      kubectl delete pvc export-ibm-minio-ow-minio-ibm-minio-1
      kubectl delete pvc export-ibm-minio-ow-minio-ibm-minio-2

   6. Apply the file that was previously saved: 

      oc apply -f minio.yaml

   7. Restart UDI services:

      oc delete pods --force `oc get pods | grep  udi | awk '{print $1}'`

2. Clear Redis keys
   1. Retrieve redis secret and copy the pass value:

      kubectl get secret redis-secret-default -o yaml | grep "pass: "
      
        pass: <pass value>
      

   2. Decode pass value that uses base64 encryption:

      echo "<pass value>" | base64 -d

   3. Start a bash session in redis pod:

      kubectl exec -ti c-default-redis-m-0 /bin/bash

   4. Authenticate to redis cli with the decoded pass value:

      redis-cli -p 6379 -a <decoded_pass value>
      Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.
      127.0.0.1:6379>
      

   5. Flush all keys by typing the following flushall instruction:

      127.0.0.1:6379> flushall
      OK
      127.0.0.1:6379>