Gather information about your foundational services installation

Get information to help with resolving IBM Cloud Pak foundational services issues in your cluster.

These commands provide information about the foundational services operators and operands that are installed in your cluster.

Identify whether the issues are related to Operand Deployment Lifecycle Manager

The commands in this section help you to identify issues with the Operand Deployment Lifecycle Manager. If these commands do not show any errors, then the issues are not related to the Operand Deployment Lifecycle Manager.

Note: The cert-manager service generates the cs-ca-certificate-secret secret, and the ibm-im-operator generates the ibmcloud-cluster-info configmap. The ibm-im-operator installation completes only after the cs-ca-certificate-secret secret is ready. Therefore, the ibm-im-operator is ready only after the operand of the ibm-cert-manager-operator is deployed.

• foundational services subscriptions

  Provides a list of installed operators in your cluster.

    oc -n <your-foundational-services-namespace> get subscription
  

  Following is a sample output:

    NAME                              PACKAGE                               SOURCE                CHANNEL
    ibm-cert-manager-operator         ibm-cert-manager-operator             opencloud-operators   stable-v1
    ibm-im-operator                  ibm-iam-operator                      opencloud-operators   stable-v1
    ibm-licensing-operator            ibm-licensing-operator-app            opencloud-operators   stable-v1
  

• foundational services ClusterServiceVersions (CSVs)

  Provides a list of operators, their CSV version, and whether they are correctly installed or not.

    oc -n <your-foundational-services-namespace> get csv
  

  Following is a sample output:

    NAME                                          DISPLAY                                VERSION   REPLACES                                      PHASE
    ibm-cert-manager-operator.v3.6.2              IBM Cert Manager Operator              3.6.2     ibm-cert-manager-operator.v3.6.1              Succeeded
    ibm-im-operator.v3.6.2                       IBM IM Operator                       3.6.2     ibm-iam-operator.v3.6.1                       Succeeded
    ibm-licensing-operator.v1.1.3                 IBM Licensing Operator                 1.1.3     ibm-licensing-operator.v1.1.2                 Succeeded
    operand-deployment-lifecycle-manager.v1.2.1   Operand Deployment Lifecycle Manager   1.2.1     operand-deployment-lifecycle-manager.v1.2.0   Succeeded
  

  Note: If all the CSVs exist, but no operand is deployed, it might be because the Operand Deployment Lifecycle Manager is waiting for the installPlan of the operator to be ready. After the installplan is ready, the Operand Deployment Lifecycle Manager deploys its operands. You can get the installPlan status by running the following command:

    oc  -n <your-foundational-services-namespace> get installplan
  

  Following is a sample output:

    NAME            CSV                                APPROVAL    APPROVED
    install-kk5fl   ibm-cert-manager-operator.v3.6.2   Automatic   true
  

  To view details about an installPlan, use the following command:

    oc describe installplan -n <your-foundational-services-namespace> <installplan-name>
  

Identify other causes

These commands provide information about the foundational services pods that are created in your cluster.

• Check the operator pod status.

    oc -n <your-foundational-services-namespace> get pod | grep operator
  

  Following is a sample output:

    ibm-cert-manager-operator-5869ccb57-8xr2x          1/1     Running                      0          4d17h
    ibm-im-operator-7c97568b59-2xqpp                  1/1     Running                      0          4d17h
    ibm-licensing-operator-784c8f5988-w5bt5            1/1     Running                      0          4d17h
  

• Check the logs of the IBM Common Service Operator and the Operand Deployment Lifecycle Manager

    oc -n openshift-operators logs -f $(oc -n openshift-operators get pod -l app.kubernetes.io/name=odlm -o jsonpath="{.items[].metadata.name}") >> logs.yaml
  

• Get a list of pods that have error

    oc -n <your-foundational-services-namespace> get pod | grep -v Running
  

  Following is a sample output:

    NAME                                               READY   STATUS                       RESTARTS   AGE
    platform-auth-service-557bcb88bb-x6dmr                          0/4     Pending                      0          4d17h
    auth-pdp-67fc7599b7-2xh8t                          0/2     OutOfcpu                     0          4d17h
    iam-onboarding-7tz44                               0/1     Init:0/5                     0          4d2h
    security-onboarding-skrpf                          0/1     Init:0/1                     0          4d17h