Loading

Troubleshooting RTF error Readiness probe failed: 409: ...

Data pubblicazione: Mar 2, 2024
Risoluzione

SYMPTOM

  • An application fails to deploy to a Runtime Fabric cluster with the following message:
Readiness probe failed: 409: <html> <head> <meta http-equiv="Content-Type" content="text/html;charset=utf-8"/>

  • Alternatively, the same error can be seen when checking the Kubernetes events for the application.

CAUSE

Apps deployed in RTF are frequently health checked by Kubernetes. In this case, the readiness check is returning the error "Readiness probe failed: 409: ...".


SOLUTION

To find out the root cause of the readiness check failure, please run the following steps:

1. SSH into an RTF controller node or enter a console in the RTF Ops Center (skip this step for RTF on Self-Managed Kubernetes).
2. Enter gravity (skip this step for RTF on Self-Managed Kubernetes): 
sudo gravity enter
3. Find the app name with the following command: 
kubectl get pods --all-namespaces | grep -i "<app name>"
Replace <app name> with the name of the application as seen in Runtime Manager.

The result should look something like this: 
1234-23534-43645-56756-323   app-name-xxxxx-xxxxx                    2/2     Running     0          72d     10.244.3.18    10.39.1.1   <none>
4. Then, based on the actual results above, run the following: 
kubectl describe pod -n 1234-23534-43645-56756-323 app-name-xxxxx-xxxxx
5. Scroll down to the last few lines of the command output, the Kubernetes events should show more details about the issue. For example: when using an incorrect API ID: 
6h24m                Warning                Unhealthy          Pod          kubelet, 10.39.1.1    Readiness probe failed: 409: API 1234567: Not Ready. API not found in the API Platform.                                                                                                                                           spec.containers{app}

6. Try to resolve the issue based on the above details. Also make sure to use the latest Mule Runtime versions which contain the latest features/bug fixes. For example, a Mule license missing the "api-gateway" entitlement caused the 409 error message. The fix to this particular issue is implemented in Mule Runtime release 4.3.0-20220124-1 for v4.3.0 and 4.4.0-20220124-2 for v4.4.0 or later. Update the application with the February 8, 2022 release or later for license entitlement issue.

7. If the error message clearly states the cause, then correct it. Refer to the related articles below for further assistance. If you are still unable to resolve the problem, then obtain a RTF lite report with "rtfctl report" command and attach it to a support case (please specify which app name is reporting the error).

Related Article

Application In RTF Stays At "Applying" Status Due to API Auto Discovery
Numero articolo Knowledge

001121258

 
Caricamento
Salesforce Help | Article