Skip to content
This repository has been archived by the owner on Feb 7, 2024. It is now read-only.

Add a hard timeout for each service update #56

Open
sinfomicien opened this issue Jun 23, 2016 · 0 comments
Open

Add a hard timeout for each service update #56

sinfomicien opened this issue Jun 23, 2016 · 0 comments

Comments

@sinfomicien
Copy link

As of today, if a server is declared in Fleet Cluster, but is in an unknown network state... You have to wait for at least 30 minutes before getting that something is wrong. Would be better to put a 'hard timeout' on the update. If the update is not finished after the timeout, cancel everything, and go to the next update.

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

1 participant