Scenario Description of Failure Symptoms

All API calls via yunapi result in errors.

Impact Scope of the Failure

• Impact on Cloud Platform product control: The control is unavailable; all API calls through yunapi are unavailable.
• Impact on users' workload: No impact on the customer's existing data workload usage.

Failure Location and Analysis

• Check if the yunapi pod status is normal.
• Check if the network environment is functioning properly.

Failure Emergency Response Steps

1. Check if the pod status is normal. If the pod status is abnormal, you can delete and restart it to quickly recover the workload.

kubectl get pod -n tce | grep tcenter-yunapi3
kubectl delete pod -n tce xxxx--tcenter-yunapi3-traefik-xxxxx

2. If restarting does not recover the workload, access the container to check if the network connection from yunapi-traefik to other services is normal. If there is a network issue, fix the network. If the issue persists, view the service logs and recover the workload.

kubectl exec -it -n tce tcloud-tcenter-yunapi3-traefik-xxxx bash
cd /usr/local/services/traefik/log
# Filter logs by page reqid.
grep -ir "reqid" traefik.log
 grep -ir "reqid" *

Failure Recovery Verification

The page successfully calls the API through yunapi.