cf mtar deployment problem

[nannam1]

Hello All,

We have 2 spaces (DEV, QA) in Cloud foundry. We have developed a MTA project (with multiple HTML modules) In DEV Apps are working fine, when i try to deploy the same MTA in QA environment its not getting deployed (BUILD is successful).

here is error:

#2.0#2019 11 05 16:18:21.121#Z#ERROR#com.sap.cloud.lm.sl.xs2.e2e107db-ffe6-11e9-9431-eeee0a822bb8.MAIN_LOG.executeTaskTask# ######com.sap.cloud.lm.sl.cf.persistence.services.ProcessLogger########flowable-async-job-executor-thread-8### [ExecuteTaskStep] Execution of task "deploy" failed. Download the application logs "ZSFLP_QA", via the dmol command, and check them for more information.# #2.0#2019 11 05 16:18:21.126#Z#ERROR#com.sap.cloud.lm.sl.xs2.e2e107db-ffe6-11e9-9431-eeee0a822bb8.MAIN_LOG.executeTaskTask# ######com.sap.cloud.lm.sl.cf.persistence.services.ProcessLogger########flowable-async-job-executor-thread-8### Exception caught# com.sap.cloud.lm.sl.common.SLException: A step of the process has failed. Retrying it may solve the issue. at com.sap.cloud.lm.sl.cf.process.steps.SyncFlowableStep.execute(SyncFlowableStep.java:67) at org.flowable.engine.impl.delegate.invocation.JavaDelegateInvocation.invoke(JavaDelegateInvocation.java:35) at org.flowable.engine.impl.delegate.invocation.DelegateInvocation.proceed(DelegateInvocation.java:35) at org.flowable.engine.impl.delegate.invocation.DefaultDelegateInterceptor.handleInvocation(DefaultDelegateInterceptor.java:26)

I tried multiple times, but no use. Please suggest to resolve the same.

[jbaukham]

I had what looks like a similar issue with similar error - I noticed the app was being deployed and appears in the list of app but was failing on startup.

When looking at the app overview on SCP, I noticed messages in the 'Most Recent Application Events' section saying the disk quota had been exceeded. The default value was 256 MB, I upped this to 512MB manually on SCP and started the app successfully.

I then updated the values in the mta.yaml file, rebuilt the mta and redeployed and all worked ok.