Skip to content
This repository has been archived by the owner on Jan 21, 2022. It is now read-only.

execution expired on bosh deploy, director unresponsive #72

Closed
shalako opened this issue Jan 13, 2014 · 1 comment
Closed

execution expired on bosh deploy, director unresponsive #72

shalako opened this issue Jan 13, 2014 · 1 comment

Comments

@shalako
Copy link
Contributor

shalako commented Jan 13, 2014

Preparing configuration
binding configuration (00:00:01)
Done 1/1 00:00:01

Started updating job ha_proxy_z1: ha_proxy_z1/0
Done updating job ha_proxy_z1: ha_proxy_z1/0
Started updating job nats_z1: nats_z1/0
Done updating job nats_z1: nats_z1/0
Started updating job postgres_z1: postgres_z1/0
Done updating job postgres_z1: postgres_z1/0
Started updating job uaa_z1: uaa_z1/0
Perform request get, https://192.168.50.4:25555/tasks/3, {"Authorization"=>"Basic YWRtaW46YWRtaW4="}, nil
REST API call exception: execution expired

maybe I'll try again

± |master ✗| → bosh deploy
Getting deployment properties from director...
Perform request get, https://192.168.50.4:25555/deployments/cf-warden/properties, {"Content-Type"=>"application/json", "Authorization"=>"Basic YWRtaW46YWRtaW4="}, nil
REST API call exception: execution expired

vagrant reload succeeded, but now director is unresponsive.

± |master ✗| → bosh deploy
Getting deployment properties from director...
Compiling deployment manifest...
HTTP 500:

now what?

@jfoley
Copy link
Contributor

jfoley commented Apr 21, 2014

Is this still an issue? If so, please reopen.

CF Community Pair (@jfoley & @jtuchscherer)

@jfoley jfoley closed this as completed Apr 21, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants