CCV2 2211 deployment faills with the e erro- Component has failing instances (CrashLoopBackOff)

[Rakesh_kp]

Here is  brief summary.

SAP version - 2211.29

Problem-

Unable to do deployment in ccv2. error"{"envCode":"d4","subCode":"40fae3520bff4d9da7e5a2b69c0f0b19","errorMsg":"Component has failing instances (CrashLoopBackOff).","stepCode":"dm_0200js","buildName":"migration_1","buildCode":"20241212.2","customerReleaseBuildVersion":"2211.29-2211azuresdk12-20241121-020431-20241212.2-aa47277-migration_1"}"

The same error occurs when every deployment, irrespective of any build. Its happening from a while now.

Its not code error rather seems Platform infra error.

logs-Nothing much in logs. the same error"{"envCode":"d4","subCode":"40fae3520bff4d9da7e5a2b69c0f0b19","errorMsg":"Component has failing instances (CrashLoopBackOff).","stepCode":"dm_0200js","buildName":"migration_1","buildCode":"20241212.2","customerReleaseBuildVersion":"2211.29-2211azuresdk12-20241121-020431-20241212.2-aa47277-migration_1"}

Appreciated any info on solution pointing on this issue.

#CCV2 deployment

#composable storefront

#crashback loop error

 SAP Commerce 

Thanks 

Rakesh

[cieslo]

This kind of issue indicates that at least one of the application pods has encountered exception that caused failure in startup and most probably is in constant restarting loop. Please make sure to check Services in Cloud Portal to identify such pods (or use Dynatrace monitoring) and check the logs for that pod(s). Usually the first error in the logs is the one that you need to check.