Verifying the Engineering Lifecycle Management instance

The Engineering Lifecycle Management instance verification includes the verification of Engineering Lifecycle Management application pods and created resources.

Verification of the created resources

You can use one of the following methods to view the resources created for the Engineering Lifecycle Management instance.

Red Hat OpenShift Container Platform web console

  1. Log in to the Red Hat® OpenShift® Container Platform web console.
  2. Click Home > Search.
  3. Select the project where you installed the Engineering Lifecycle Management instance from the Project list.
  4. Select the resources from the Resources list.
    Note: You can select one or more resources from the list. The list includes Deployment, Pod, Service, Networkpolicy, Route, Configmap, Serviceaccount, PersistentVolumeClaim, RoleBinding, Role

Red Hat OpenShift CLI

  1. Log in to the Red Hat OpenShift command line.
  2. Run the following command 
    oc get elm/<elm-instance-name> -o custom-columns="Name:.metadata.name, Status:.status.conditions[?(@.status=='True')].type" -n <namespace-name>
    oc get elm/example-elm -o custom-columns="Name:.metadata.name, Status:.status.conditions[?(@.status=='True')].type" -n example
    The following examples help you to familiarize the syntax of the command.
    oc get Deployment,Pod,Service,Networkpolicy,Route,Configmap,Serviceaccount,PersistentVolumeClaim,RoleBinding,Role -l app.kubernetes.io/managed-by=ibm-elm-operator -n <namespace-name>
    oc get Deployment,Pod,Service,Networkpolicy,Route,Configmap,Serviceaccount,PersistentVolumeClaim,RoleBinding,Role -l app.kubernetes.io/managed-by=ibm-elm-operator -n example
    namespace-name
    Namespace or project name where the Engineering Lifecycle Management instance is installed.
    elm-instance-name
    Name of the Engineering Lifecycle Management resource.

Kubernetes CLI

  1. Log in to the Kubernetes cluster using command line.
  2. Run the following command 
    kubectl get elm/<elm-instance-name> -o custom-columns="Name:.metadata.name, Status:.status.conditions[?(@.status=='True')].type" -n <namespace-name>
    kubectl get elm/example-elm -o custom-columns="Name:.metadata.name, Status:.status.conditions[?(@.status=='True')].type" -n example
    The following examples help you to familiarize the syntax of the command.
    kubectl get Deployment,Pod,Service,Networkpolicy,Ingress,Configmap,Serviceaccount,PersistentVolumeClaim,RoleBinding,Role -l app.kubernetes.io/managed-by=ibm-elm-operator -n <namespace-name>
    kubectl get Deployment,Pod,Service,Networkpolicy,Ingress,Configmap,Serviceaccount,PersistentVolumeClaim,RoleBinding,Role -l app.kubernetes.io/managed-by=ibm-elm-operator -n example
    namespace-name
    Namespace or project name where the Engineering Lifecycle Management instance is installed.
    elm-instance-name
    Name of the Engineering Lifecycle Management resource.

Verify the resources created for the Engineering Lifecycle Management instance

Resource category
Created resources
Deployment
  • ibm-elm-operatorcontroller-manager
  • ibm-elm-ccm
  • ibm-elm-dcc
  • ibm-elm-gc
  • ibm-elm-jas
  • ibm-elm-rb
  • ibm-elm-jts
  • ibm-elm-ldx
  • ibm-elm-lqe
  • ibm-elm-qm
  • ibm-elm-eni
  • ibm-elm-rm
Service
  • ibm-elm-operatorcontroller-manager-service
  • ibm-elm-ccm
  • ibm-elm-dcc
  • ibm-elm-gc
  • ibm-elm-jas
  • ibm-elm-rb
  • ibm-elm-jts
  • ibm-elm-ldx
  • ibm-elm-lqe
  • ibm-elm-qm
  • ibm-elm-eni
  • ibm-elm-rm
Pod
  • ibm-elm-operatorcontroller-manager-XXXXX
  • ibm-elm-ccm-XXXXX
  • ibm-elm-dcc-XXXXX
  • ibm-elm-gc-XXXXX
  • ibm-elm-jas-XXXXX
  • ibm-elm-rb-XXXXX
  • ibm-elm-jts-XXXXX
  • ibm-elm-ldx-XXXXX
  • ibm-elm-lqe-XXXXX
  • ibm-elm-qm-XXXXX
  • ibm-elm-eni-XXXXX
  • ibm-elm-rm-XXXXX
NetworkPolicies
<ELM instance name>-network-policy
Route or Ingress
  • ccm-<route/ingress>
  • dcc-<route/ingress>
  • gc-<route/ingress>
  • jazzop
  • rb-<route/ingress>
  • jts-<route/ingress>
  • ldx-<route/ingress>
  • lqe-<route/ingress>
  • oidc
  • qm-<route/ingress>
  • eni-<route/ingress>
  • rm-<route/ingress>
  • saml
  • scim
ConfigMap
  • ccm-config
  • dcc-config
  • gc-config
  • jas-config
  • rb-config
  • jts-config
  • ldx-config
  • lqe-config
  • qm-config
  • eni-config
  • rm-config
ServiceAccount
  • elm-service-account
  • ibm-elm-operator-service-account
PersistentVolumeClaims
  • ccm-pvc
  • dcc-pvc
  • gc-pvc
  • jas-pvc
  • rb-pvc
  • jts-pvc
  • ldap-pvc
  • ldx-pvc
  • lqe-pvc
  • qm-pvc
  • eni-pvc
  • rm-pvc
RoleBindings
elm-role-binding
Role
elm-role

Verify the status of the Engineering Lifecycle Management instance

Table 1. Engineering Lifecycle Management reconciliation conditions
Resource category Status Meaning of the status
Prerequisite reconciliation Failed Prerequisite reconciliation failed. Check the Reason and Message column for details about the error.
In Progress The reconciliation process is running.
Completed Prerequisite reconciliation is completed.
Security reconciliation Failed Security reconciliation failed. Check the Reason and Message column for details about the error.
In Progress The operator is checking the network policy and RBAC.
Completed Security reconciliation is completed.
Certificate management reconciliation Failed Certificate reconciliation from Cert Manager failed. Check the Reason and Message column for details about the error.
In Progress Cert Manager is reconciling the certificate resources.
Completed Certificate reconciliation is completed.
Engineering Lifecycle Management reconciliation Failed Engineering Lifecycle Management Kubernetes resources reconciliation failed. Check the Reason and Message column for details about the error. To check the Kubernetes resource creation condition, see the following Creation events table.
In Progress The operator is reconciling the config maps, secrets, routes, role, role bindings, services, and PVC.
Completed Engineering Lifecycle Management reconciliation is completed.
Table 2. Creation events
Resource category Status Meaning of the status
Engineering Lifecycle Management validations Failed Missing the pre-req information for the Engineering Lifecycle Management setup. Check the Reason and Message column for details about the error.
In Progress Operator is validating all the files that are required for the Engineering Lifecycle Management instance setup.
Completed Validation is completed.
Kubernetes resource creation Failed Kubernetes resources are not created. Check the Reason and Message column for details about the error.
In Progress Reconciliation of the Kubernetes resources for the Engineering Lifecycle Management instance is running.
Completed Kubernetes resource for the Engineering Lifecycle Management instance is created.
Initialization Failed Failed to initialize Engineering Lifecycle Management applications.
In Progress Engineering Lifecycle Management initialization is in progress.
Completed Initialization of all the Engineering Lifecycle Management applications is completed.
Engineering Lifecycle Management setup Failed One or more Engineering Lifecycle Management applications failed during setup. Check the Reason and Message column for details about the error. To understand the error at the application level, see the following Applications events table.
In Progress Engineering Lifecycle Management instance setup is running.
Completed Engineering Lifecycle Management instance setup is completed and all applications are ready.
Engineering Lifecycle Management post setup Failed Engineering Lifecycle Management post setup check failed. Check the Reason and Message column for details about the error.
In Progress Engineering Lifecycle Management post setup is running.
Completed Engineering Lifecycle Management post setup check is completed.
Table 3. Application events
Resource category Status Meaning of the status
<ELM app sort name> JTS Failed Application failed in setup/reconciliation/upgrade. Check the Reason and Message column for details about the error. You can check the application logs for more details.
In Progress Application setup/reconciliation/upgrade is in progress.
Completed Application is ready.
Note: For a successful Engineering Lifecycle Management installation, you can review and make sure all the conditions in the table 2, 3, and 4 have the completed status. And, the Application events show the status as The JTS application is ready.

Log in to the application by using routes

  • In the Red Hat OpenShift Container Platform web console, select Networking > Routes.
  • From the Project list, select the project where you installed the Engineering Lifecycle Management instance from the Project list.
  • Click the URL available in the Location field of the application that you want to login.
  • Log in to the application by using your user ID and password. The Engineering Lifecycle Management application opens.