-
Notifications
You must be signed in to change notification settings - Fork 657
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
registry hangs and is unresponsive: bosh deploy fails with execution expired #1234
Labels
Comments
Updating fog and excon sounds ok. |
I've created https://www.pivotaltracker.com/story/show/119363951 to bump fog in bosh-registry. |
beyhan
pushed a commit
that referenced
this issue
Jun 30, 2016
- consume fixes in excon 0.49, especially freezing connections in the registry - fixes #1234 - get rid of full fog (we only need fog-aws and fog-openstack) - some other gems were taken in newer version by `bundle update bosh_openstack_cpi` [#119363951](https://www.pivotaltracker.com/story/show/119363951) Signed-off-by: Beyhan Veli <beyhan.veli@sap.com>
beyhan
pushed a commit
that referenced
this issue
Jun 30, 2016
- consume fixes in excon 0.49, especially freezing connections in the registry - fixes #1234 - get rid of full fog (we only need fog-aws and fog-openstack) - some other gems were taken in newer version by `bundle update bosh_openstack_cpi` [#119363951](https://www.pivotaltracker.com/story/show/119363951) Signed-off-by: Beyhan Veli <beyhan.veli@sap.com>
beyhan
pushed a commit
that referenced
this issue
Jul 1, 2016
- consume fixes in excon 0.49, especially freezing connections in the registry - fixes #1234 - get rid of full fog (we only need fog-aws and fog-openstack) - some other gems were taken in newer version by `bundle update bosh_openstack_cpi` [#119363951](https://www.pivotaltracker.com/story/show/119363951) Signed-off-by: Beyhan Veli <beyhan.veli@sap.com>
Kiemes
pushed a commit
that referenced
this issue
Sep 6, 2016
- consume fixes in excon 0.49, especially freezing connections in the registry - fixes #1234 - get rid of full fog (we only need fog-aws and fog-openstack) - some other gems were taken in newer version by `bundle update bosh_openstack_cpi` [#119363951](https://www.pivotaltracker.com/story/show/119363951) Signed-off-by: Tom Kiemes <tom.kiemes@sap.com>
Fixed with bosh 257.14 |
jianqiu
pushed a commit
to zhanggbj/bosh
that referenced
this issue
Feb 25, 2017
- consume fixes in excon 0.49, especially freezing connections in the registry - fixes cloudfoundry#1234 - get rid of full fog (we only need fog-aws and fog-openstack) - some other gems were taken in newer version by `bundle update bosh_openstack_cpi` [#119363951](https://www.pivotaltracker.com/story/show/119363951) Signed-off-by: Tom Kiemes <tom.kiemes@sap.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We saw recently a few deployments failing with the error of
execution expired
during writing the settings for a VM into the registry. The registry stopped responding at all, there was nothing in the logs.Even when being on the Director itself, calling the registry didn't work. Something like
should fail with an error saying
instance 'bla' not found
, but just hangs until it runs into a read timeout.So we attached a
gdb
and looked at the backtrace, seeing that excon couldn't open thessl_socket
and blocked forever in the rescue. Note that the documentation ofIO.select
states this piece of code as an explicit example on how to implement a blocking readThe
gdb
stacktracke:This is an acepted bug in excon 0.45.4 and has been fixed by adding a timeout to
IO.select
in 0.49.fog-core
is already updated to consume excon 0.49. We're now waiting for fog and fog-openstack to be updated to consume fog-core 1.38.0.While this prevents excon from blocking forever, it might be a good idea to have a detailed look at the registry on what else could be done to prevent one hanging call blocking the entire registry for everyone.
The text was updated successfully, but these errors were encountered: