Home
Troubleshooting
This guide describes how to analyze and resolve some of the common problems that you might encounter while you work with HCL OneTest™ Server.
Troubleshooting issues
You can find information about the issues or problems that you might encounter while working with HCL® OneTest™ Data. Details about issues, their causes and the resolutions that you can apply to fix the issues are described.
Commands used in HCL OneTest Data
When you want to view the list of HCL® OneTest™ Data pods and to manage each of these pods, you can run the kubectl or oc commands on an SSH console.

Troubleshooting
This guide describes how to analyze and resolve some of the common problems that you might encounter while you work with HCL OneTest™ Server.
- Troubleshooting issues
  You can find information about the issues or problems that you might encounter while working with HCL OneTest™ Server. Details about issues, their causes and the resolutions that you can apply to fix the issues are described.
- Troubleshooting issues
  You can find information about the issues or problems that you might encounter while working with HCL® OneTest™ Data. Details about issues, their causes and the resolutions that you can apply to fix the issues are described.
  - Schema designing error or warning messages
    The HCL® OneTest™ Data analyzer validates the logical and structural consistency of the data definition of a schema. In case of any inconsistency in the schema structure, the analyzer issues error or warning messages based on the type of the analysis.
  - Compile-time error messages
    When you generate the test data of a schema, you might encounter compile-time error messages. The schemas with compilation errors fail to generate the test data. You can view the error messages on the schema designer.
  - Configuring log files
    When you run into issues to trace the log files or the log files end abruptly without the complete information about the action, you must configure settings for the log file in the configMap file.
  - Audit log overview
    When execution of a map to generate the test data fails, HCL® OneTest™ Data creates an audit log. The audit log records the detailed information about the execution of the failed job.
  - Commands used in HCL OneTest Data
    When you want to view the list of HCL® OneTest™ Data pods and to manage each of these pods, you can run the kubectl or oc commands on an SSH console.
  - Troubleshooting installation issues
    You might encounter issues when you access HCL® OneTest™ Data after you install HCL OneTest Server for the first time. You can find details about the issues, their causes, and resolutions to fix those issues.

Commands used in HCL OneTest Data

When you want to view the list of HCL® OneTest™ Data pods and to manage each of these pods, you can run the kubectl or oc commands on an SSH console.

The following table provides you the list of commands that you can use to manage the pods on the Kubernetes environment (k3s):

Commands	Purpose	Examples
`kubectl get pods`	Shows the list of all pods with the status of each pod.	-
`kubectl get configmaps`	Shows the list of all configuration files.	-
`kubectl exec -it <podname> bash`	Helps to access the pod.	`kubectl exec -it {my-ots}-data-app -0 bash`
`kubectl edit configmap -n <namespace> <configmapName> -o yaml`	Edits the configuration file.	`kubectl edit configmap -n test-system {my-ots}-data-config -o yaml`
`kubectl delete pod <podname>`	Deletes and restart the pod.	`kubectl delete pod {my-ots}-data-app-0`
`kubectl logs <podname>`	Shows the logs of any specific pod.	`kubectl logs {my-ots}-data-app-0`

The following table provides you the list of commands that you can use to manage the pods on the Red Hat OpenShift server:

Commands	Purpose	Examples
`oc get pods`	Shows the list of all pods with the status of each pod.	-
`oc get configmaps`	Shows the list of all configuration files.	-
`oc exec -it <podname> bash`	Helps to access the pod.	`oc exec -it {my-ots}-data-app -0 bash`
`oc edit configmap -n <namespace> <configmapName> -o yaml`	Edits the configuration file.	`oc edit configmap -n test-system {my-ots}-data-config -o yaml`
`oc delete pod <podname>`	Deletes and restart the pod.	`oc delete pod {my-ots}-data-app-0`
`oc logs <podname>`	Shows the logs of any specific pod.	`oc logs {my-ots}-data-app-0`