Checking the status of each component
To check the full status of the created IBM RPA instance, follow these steps:
-
In the OpenShift console, go to the Installed Operators page under Operators.
-
Select the project that you installed the operator in, then the IBM Robotic Process Automation operator.
-
Go to the Robotic Process Automation
-
Click on IBM RPA instance and then on the Details tab.
You click on rpa-sample and then on the details tab
Optional: Alternatively, you can run the following command, to see the full CR status, replacing <PROJECT>
with the one the IBM RPA instance is installed.
$ oc describe roboticprocessautomation -n <PROJECT>
Status:
Conditions:
Last Transition Time: 2022-03-25T13:59:56Z
Message: RPA successfully installed
Reason: Installed
Status: True
Type: Ready
Endpoints:
Ca Secret:
Key: ca.crt
Secret Name: <UI certificate secret name>
Name: ui
Scope: External
Type: UI
Uri: <UI external URL>
Managed Resources:
Versions:
Available:
Channels:
Name: v1.3
Name: v1.2
Name: v1.1
Name: v1.0
Versions:
Name: 1.3.0
Name: 1.2.0
Name: 1.2.1
Name: 1.2.2
Name: 1.2.3
Name: 1.2.4
Name: 1.2.5
Name: 1.1.0
Name: 1.1.1
Name: 1.0.0
Reconciled: 1.2.2
Conditions
IBM RPA supports Kubernetes Conditions. These Conditions can be viewed as a snapshot of the current and most up-to-date status of the IBM RPA instance.
- The
Ready
condition will be setTrue
when all of the Pods in theStatefulSet
are Ready, and all the conditions below have been removed. - The
Error
condition will be setTrue
when an error is encountered during reconciliation of the IBM RPA instance. The Reason and Message should have details regarding what the error may have been. - The
RedisNotReady
condition will be setTrue
whenIBM RPA
instance if first created. Once theIBM RPA
instance is connected to theRedis
service, this condition will be removed. - The
ZenNotReady
condition will be setTrue
whenIBM RPA
instance if first created. Once theIBM RPA
instance is connected to theZen
service, this condition will be removed. - The
OCRNotReady
condition will be setTrue
whenIBM RPA
instance if first created. Once theocr
pod is created and ready, this condition will be removed. - The
AntivirusNotReady
condition will be setTrue
whenIBM RPA
instance if first created. Once theantivirus
pods are created and ready, this condition will be removed. - The
UINotReady
condition will be setTrue
whenIBM RPA
instance if first created. Once theui
pod is created and ready, this condition will be removed. - The
APIServerNotReady
condition will be setTrue
whenIBM RPA
instance if first created. Once theapi-server
pod is created and ready, this condition will be removed. - New on 21.0.3: The
NLPNotReady
condition will be setTrue
whenIBM RPA
instance if first created. Once the NLP runtime pod is created and ready, this condition will be removed. - New on 21.0.3: The
DefaultRedisPassword
is set toTrue
if the Redis password was generated by the operator. This can only be removed by re-installing IBM RPA with an existing Redis Secret in the namespace (Link to the install pre-reqs). This will not stop the IBM RPA instance from reaching a "Ready" state. - New on 21.0.3: The
DefaultAPIServerKey
is set toTrue
is the API Server API key is generated by the operator. Change this key to remove this warning. This will not stop the IBM RPA instance from reaching a "Ready" state.
Versions
The Versions
status provides information about the currently reconciled version of the operand (IBM RPA), as well as the available versions and channels the operator supports.
A channel, such as v1.2
, allows for a user to subscribe to a stream of releases. When initially deployed with the version property in the CR spec set to a channel, the operator will automatically install the latest available version
within that channel. When new versions are released in that channel, the operands (CR instances) will automatically be upgraded by the operator.
The currently reconciled version
will always be available in status.versions.reconciled
, even if the version specified in the CR spec is a channel.
Endpoints
The Endpoints
status provides information about the internal and external routes available for connecting with the IBM RPA instance.
The secret containing the CA certificate for the route as well as the route URL is provided in the status for all created routes.