-
Notifications
You must be signed in to change notification settings - Fork 594
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error in step cloudFoundryDeploy: running command 'cf' failed [ref:#3297] #3817
Comments
Hi @nuramon9999 , Could you please point me to your pipelines to access the logs? The error here looks too generic |
I'm also facing same issue. Any resolution yet? |
Hello, |
For us yes. It was an issue of not having enough memory for us. For the final deployment step, we temporarily have two instances of our app running, which meant that we needed double the amount of quota for the step. Weird thing was, that after it running fine once we could reduce it back downto the typical parameters that we needed and it worked fine. Depending on the issue there should be more in your logs. Tomorrow I would be able to show some more info and how we found out about the problem. |
Hi @nuramon9999 , |
Hello, I am also facing this issue. My deployment shows successful but I get error at the end: 11:14:41 info cloudFoundryDeploy - Step telemetry data:{"StepStartTime":"2023-08-04 05:42:01.981580358 +0000 UTC","PipelineURLHash":"3e75fc5d13dfe22db53dbd84eeab769ba418d39b","BuildURLHash":"45f7332196ecf3ce7bd40af8fec501d1cfe3f12d","StageName":"Deploy Mock","StepName":"cloudFoundryDeploy","ErrorCode":"0","StepDuration":"159831","ErrorCategory":"undefined","CorrelationID":"https://gkerefappscicd.jaas-gcp.cloud.sap.corp/job/s4h-ext-mission/1065/","PiperCommitHash":"ff5eddfb7cbc5fc50e7947ed852de2eae96e12ed","ErrorDetail":null} There's no specific info about the error to dig into.Please help me here. Thanks in advance. |
Hello Shubham, I can only refer you to our memory solution that actually solved this for us. We had a certain amount of ram, gave some more to the application and all of a sudden the build went through. We just removed the ram again afterwards. because on paper the application is running fine with the amount of ram we had dedicated to it. Sorry, that I do not have a clearer solution for you. With our issue, we also found a remark of the memory we used and it not having enough memory, even though we were on 2.4Gb and had 4 available. The only thing that made sense to us seems to be, that during the build, the application already allocates its ram, while the old application still blocks its memory for a short time. Good luck, |
ref:#3297
Hello,
The once vanished error is back and with that I will try to supply the necessary information.
We also recently updated jenkins and are unsure as to if that might be a factor in the unsuccessful runs.
The first error occurs in this step: /piper cloudFoundryDeploy
— Shell Script
Later errors refer to the shown issue:
How do we get the deploy stage to pass?
Best of wishes,
Pascal Ehrlich.
The text was updated successfully, but these errors were encountered: