組織を選択
Application In CloudHub 2.0 Stays In "Applying" Status Due to API Autodiscovery
公開日: Jan 17, 2025
説明
An application remains in the "Applying" state when deploying it to a CloudHub 2.0 space.
An application has an API Autodiscovery configured.
Upon checking the network logs with a browser developer tools or after taking a HAR file the following can be observed:
Response body:
"replicas": [
{
"id": "american-flights-support-app-ch20-655d55766d-sgpwp",
"state": "STARTING",
"deploymentLocation": "0e98a641-e5ff-4d46-b407-8e6e5dc58eb9",
"currentDeploymentVersion": "58c49e85-184e-4ee4-819c-336d700cfb58",
"reason": " Readiness probe failed: 409: API 19309451: Not Ready. Awaiting for successful API tracking.\n"
},
{
"id": "american-flights-support-app-ch20-85457b66b9-drsbh",
"state": "STARTING",
"deploymentLocation": "0e98a641-e5ff-4d46-b407-8e6e5dc58eb9",
"currentDeploymentVersion": "412451eb-d3c3-4a24-ae11-ae01dbc30c73",
"reason": " Readiness probe failed: 409: API 19309451: Not Ready. Awaiting for successful API tracking.\n"
}
],In particular here:
"reason": " Readiness probe failed: 409: API 19309451: Not Ready. Awaiting for successful API tracking.\n"解決策
It usually happens when the Anypoint Platform credentials are not specified correctly.
It may be a typo in the respective property name or the wrong client_id or client_secret.
To obtain the correct credentials refer to Obtaining Environment Credentials (Recommended)
To set the credentials for your application correctly refer to https://docs.mulesoft.com/mule-gateway/mule-gateway-org-credentials-mule4#manual-configuration-2
Credential properties can also be set via Maven configuration. Refer to CloudHub 2.0 Deployment Parameters Reference for more information.
ナレッジ記事番号
002186091
この記事で問題は解決されましたか?
ご意見をお待ちしております。
