CF Job Failure


Gupta, Abhik
 

Hi,
We are trying to push a node.js application using the Cloud Controller REST APIs. The flow that we follow is similar to the flow followed by CF CLI:

Create Application Metadata > Create Route Metadata > Associate Route with Application > Get cached resources from Cloud Foundry using the Resource Match API > Upload the bits (sending the fingerprints + application.zip) asynchronously > Poll for the Job Status

This flow works perfectly fine till the last step but the polling for the job status gives back an error response like:

{
"metadata": {
"guid": "cd5bf18d-249b-4f00-9ee9-6328081d3d77",
"created_at": "2016-04-18T10:55:29Z",
"url": "/v2/jobs/cd5bf18d-249b-4f00-9ee9-6328081d3d77"
},
"entity": {
"guid": "cd5bf18d-249b-4f00-9ee9-6328081d3d77",
"status": "failed",
"error": "Use of entity>error is deprecated in favor of entity>error_details.",
"error_details": {
"error_code": "UnknownError",
"description": "An unknown error occurred.",
"code": 10001
}
}
}

Apparently, this error is also pretty well-known because it's documented in the API documentation as well here: http://apidocs.cloudfoundry.org/228/jobs/retrieve_job_with_unknown_failure.html
What could be the reason for this error from the Controller?

Thanks & Regards
Abhik


Daniel Mikusa
 

On Mon, Apr 18, 2016 at 7:10 AM, Gupta, Abhik <abhik.gupta(a)sap.com> wrote:

Hi,

We are trying to push a node.js application using the Cloud Controller
REST APIs. The flow that we follow is similar to the flow followed by CF
CLI:



Create Application Metadata > Create Route Metadata > Associate Route with
Application > Get cached resources from Cloud Foundry using the Resource
Match API > Upload the bits (sending the fingerprints + application.zip)
asynchronously > Poll for the Job Status



This flow works perfectly fine till the last step but the polling for the
job status gives back an error response like:



{

"metadata": {

"guid": "cd5bf18d-249b-4f00-9ee9-6328081d3d77",

"created_at": "2016-04-18T10:55:29Z",

"url": "/v2/jobs/cd5bf18d-249b-4f00-9ee9-6328081d3d77"

},

"entity": {

"guid": "cd5bf18d-249b-4f00-9ee9-6328081d3d77",

"status": "failed",

"error": "Use of entity>error is deprecated in favor of
entity>error_details.",

"error_details": {

"error_code": "UnknownError",

"description": "An unknown error occurred.",

"code": 10001

}

}

}
Does the app actually push and get started? i.e. if you run `cf apps`
after you get this message is the app up and running? Also, do you see
similar issues when you push with `cf push`?




Apparently, this error is also pretty well-known because it’s documented
in the API documentation as well here:
http://apidocs.cloudfoundry.org/228/jobs/retrieve_job_with_unknown_failure.html

What could be the reason for this error from the Controller?
Take a look at the cloud controller logs,
`/var/vcap/sys/log/cloud_controller_ng`. There should be more information
about the problem there.

Dan


Nicholas Calugar
 

Hi Abhik,

Another bit of information that would be interesting is whether or not you
can push your app using the CLI.


Thanks,

Nick

On Mon, Apr 18, 2016 at 6:13 AM, Daniel Mikusa <dmikusa(a)pivotal.io> wrote:

On Mon, Apr 18, 2016 at 7:10 AM, Gupta, Abhik <abhik.gupta(a)sap.com> wrote:

Hi,

We are trying to push a node.js application using the Cloud Controller
REST APIs. The flow that we follow is similar to the flow followed by CF
CLI:



Create Application Metadata > Create Route Metadata > Associate Route
with Application > Get cached resources from Cloud Foundry using the
Resource Match API > Upload the bits (sending the fingerprints +
application.zip) asynchronously > Poll for the Job Status



This flow works perfectly fine till the last step but the polling for the
job status gives back an error response like:



{

"metadata": {

"guid": "cd5bf18d-249b-4f00-9ee9-6328081d3d77",

"created_at": "2016-04-18T10:55:29Z",

"url": "/v2/jobs/cd5bf18d-249b-4f00-9ee9-6328081d3d77"

},

"entity": {

"guid": "cd5bf18d-249b-4f00-9ee9-6328081d3d77",

"status": "failed",

"error": "Use of entity>error is deprecated in favor of
entity>error_details.",

"error_details": {

"error_code": "UnknownError",

"description": "An unknown error occurred.",

"code": 10001

}

}

}
Does the app actually push and get started? i.e. if you run `cf apps`
after you get this message is the app up and running? Also, do you see
similar issues when you push with `cf push`?




Apparently, this error is also pretty well-known because it’s documented
in the API documentation as well here:
http://apidocs.cloudfoundry.org/228/jobs/retrieve_job_with_unknown_failure.html

What could be the reason for this error from the Controller?
Take a look at the cloud controller logs,
`/var/vcap/sys/log/cloud_controller_ng`. There should be more information
about the problem there.

Dan



Gupta, Abhik
 

Hi Nick, Hi Daniel,
The app push using the CLI works. I haven’t had the chance to check the cloud controller logs yet—that’s the next thing on my plate.

Best Regards,
Abhik

From: Nicholas Calugar [mailto:ncalugar(a)pivotal.io]
Sent: Tuesday, April 19, 2016 2:31 AM
To: Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org>
Subject: [cf-dev] Re: Re: CF Job Failure

Hi Abhik,

Another bit of information that would be interesting is whether or not you can push your app using the CLI.


Thanks,

Nick

On Mon, Apr 18, 2016 at 6:13 AM, Daniel Mikusa <dmikusa(a)pivotal.io<mailto:dmikusa(a)pivotal.io>> wrote:
On Mon, Apr 18, 2016 at 7:10 AM, Gupta, Abhik <abhik.gupta(a)sap.com<mailto:abhik.gupta(a)sap.com>> wrote:
Hi,
We are trying to push a node.js application using the Cloud Controller REST APIs. The flow that we follow is similar to the flow followed by CF CLI:

Create Application Metadata > Create Route Metadata > Associate Route with Application > Get cached resources from Cloud Foundry using the Resource Match API > Upload the bits (sending the fingerprints + application.zip) asynchronously > Poll for the Job Status

This flow works perfectly fine till the last step but the polling for the job status gives back an error response like:

{
"metadata": {
"guid": "cd5bf18d-249b-4f00-9ee9-6328081d3d77",
"created_at": "2016-04-18T10:55:29Z",
"url": "/v2/jobs/cd5bf18d-249b-4f00-9ee9-6328081d3d77"
},
"entity": {
"guid": "cd5bf18d-249b-4f00-9ee9-6328081d3d77",
"status": "failed",
"error": "Use of entity>error is deprecated in favor of entity>error_details.",
"error_details": {
"error_code": "UnknownError",
"description": "An unknown error occurred.",
"code": 10001
}
}
}

Does the app actually push and get started? i.e. if you run `cf apps` after you get this message is the app up and running? Also, do you see similar issues when you push with `cf push`?


Apparently, this error is also pretty well-known because it’s documented in the API documentation as well here: http://apidocs.cloudfoundry.org/228/jobs/retrieve_job_with_unknown_failure.html
What could be the reason for this error from the Controller?

Take a look at the cloud controller logs, `/var/vcap/sys/log/cloud_controller_ng`. There should be more information about the problem there.

Dan