VMware Telco Cloud Service Assurance Installation issue

VMware Telco Cloud Service Assurance installation is triggered by the execution of CLI called the tcxctl. For information on using tcxctl, see Using tcxctl Commands in the VMware Telco Cloud Service Assurance Deployment Guide.

Attach the tcxctl.log file located in the same directory as the tcxctl CLI binary in the deployer bundle.

Set the KUBECONFIG variable to your clusters kubeconfig file using command:

export KUBECONFIG=/root/.kube/<your-kubernetes-cluster-kubeconfig-file>

Use the following kubectl commands to help narrow down the issue. Also, you can attach the output of each kubectl command in your support request:
1. Get the current product status:
```
kubectl get tcxproduct -A
```
2. If the message appears: The following App CRs are still reconciling" or The following App CRs failed, check the status of each App in the message by running the following command:
```
kubectl describe app <app-name> -n <app-namespace>
```
3. In the output of the above command, look for the Useful Error Message at the bottom. This message provides adequate information about the exact resource (Deployment, StatefulSet, ReplicaSet, Job, and so on..) that is failing.
4. Depending on the resource that is failing or stuck Reconciling, run the kubectl describe command for that resource to get more information:
```
kubectl describe deployment <deployment-name> -n <namespace> or,
kubectl describe service <service-name> -n <namespace> or,
kubectl describe statefulset <statefulset-name> -n <namespace> or,
kubectl describe daemonset <daemonset-name> -n <namespace> or,
kubectl describe job <job-name> -n <namespace> or,
```
5. Once you have narrowed down to the appropriate resource, if the above commands do not provide adequate information get information from the pods owned by the resource:
```
kubectl get pods -A | grep <app-name>
kubectl describe pod <pod-name>  -n <pod-namespace>   # where pod-name and pod-namespace is the name and namespace of the pod obtained from previous command
and..
kubectl logs <pod-name>  -n <pod-namespace>
```
6. Get product installation logs. Product installation is executed by a service called Admin Operator. The logs of the installation can be obtained from the admin-operator pod by running the following steps:
```
kubectl get pods -A | grep admin-operator
```
```
kubectl logs <admin-operator-pod-name>. -n <pod-namespace> # Where <admin-operator-pod-id> is the pod id from the previous command
```
Attach these logs while filing a support request.