-
Notifications
You must be signed in to change notification settings - Fork 20
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
Some commands can hang for very long periods before failing; please consider adding timeout #104
Comments
how long is too long? what about deployments with a slow download connection? |
Fixes: ceph#104 Signed-off-by: Nathan Cutler <[email protected]>
The timeout could be configurable, and default to a large number, like one hour. |
Maybe we can improve this, if we separate the pull from calling bootstrap? |
We already did that. Images are pulled before bootstrap. |
Normally the |
we need to fix the underlying cause of this. Please have a look at where |
Indeed. Yesterday I found out that |
can we close this? |
I was not able to reproduce this issue. One situation where If there's any other situation where a timeout is still mission feel free to reopen or submit a separate issue for that. |
Certain commands, like "cephadm bootstrap" and
podman pull
can conceivably get stuck and hang for long periods of time, or even "forever".It's worth considering to precede these commands with
timeout
.This is not just for interactive users sitting at a console - the primary purpose is to ensure that CI jobs fail within a reasonable amount of time when commands get stuck.
The text was updated successfully, but these errors were encountered: