Error starting application - Stager error: stager_client staging failed: staging failed

[ashishjain14]

I am running BOSH-Lite on vagrant box Here are my environment details:
+----------------+---------------+-------------+
| Name | Versions | Commit Hash |
+----------------+---------------+-------------+
| cf | 274+dev.1* | b94315a |
| cflinuxfs2 | 1.156.0* | 3c0b2cb2+ |
| diego | 1.26.0+dev.1* | 482596a |
| garden-runc | 1.9.3* | 55956f4 |
+----------------+---------------+-------------+

I have been able to successfully deploy CF and when I execute a CF push for an application I see the following error.

Staging app and tracing logs...
Unexpected Response
Response code: 500
CC code: 170011
CC error code: CF-StagerError
Request ID: 867808c9-338b-4df1-6ddf-9bfc12fb0f0f
Request ID: 024b4ab7-26f3-497b-6cc4-f46b091cb90e::d11fe4ef-0db3-49df-a9d1-56b09e07cf09
Description: Stager error: stager_client staging failed: staging failed
FAILED

Further investigation from the stager log and looks like the certificate has expired.

"timestamp":"1506439841.812020779","source":"stager","message":"stager.staging-handler.staging-request.do-request.doing-request","log_level":0,"data":{"attempt":3,"request_path":"/v1/tasks/desire.r2","session":"3.22.1","staging-guid":"0b3813b0-1a21-47e3-80ad-23465e0a57f3"}}
{"timestamp":"1506439841.818843842","source":"stager","message":"stager.staging-handler.staging-request.do-request.failed-doing-request","log_level":2,"data":{"error":"Post https://bbs.service.cf.internal:8889/v1/tasks/desire.r2: x509: certificate has expired or is not yet valid","session":"3.22.1","staging-guid":"0b3813b0-1a21-47e3-80ad-23465e0a57f3"}}
{"timestamp":"1506439842.321335077","source":"stager","message":"stager.staging-handler.staging-request.staging-failed","log_level":2,"data":{"error":"Post https://bbs.service.cf.internal:8889/v1/tasks/desire.r2: x509: certificate has expired or is not yet valid","session":"3.22","staging-guid":"0b3813b0-1a21-47e3-80ad-23465e0a57f3","staging-request":{"app_id":"0b3813b0-1a21-47e3-80ad-23465e0a57f3","file_descriptors":16384,"memory_mb":1024,"disk_mb":4096,"environment":[{"name":"CF_STACK","value":"cflinuxfs2"},{"name":"VCAP_APPLICATION","value":"{"cf_api":"https://api.bosh-lite.com","limits":{"fds":16384,"mem":1024,"disk":4096},"application_name":"cf-nodejs","application_uris":["cf-nodej

And here are the log snippets from bbs logs

2017/09/26 15:36:06 http: TLS handshake error from 10.244.16.6:36602: remote error: tls: bad certificate
2017/09/26 15:36:06 http: TLS handshake error from 10.244.16.5:47076: remote error: tls: bad certificate
2017/09/26 15:36:07 http: TLS handshake error from 10.244.16.6:36620: remote error: tls: bad certificate

So this seems to be the actual issue with staging the application. How can I about generating new certificates?

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/151447092

The labels on this github issue will be updated when the story is started.

[software-engineer-mj]

Did you deploy your application on bosh-lite? A fix has been included in Diego v1.26.1.
Related Commit: 12708d5
Diego Release: https://github.com/cloudfoundry/diego-release/releases/tag/v1.26.1

[ashishjain14]

@kmj940101 thanks a lot, this seems to have fixed the issue 👍 . Closing this issue.