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

Discuss: Fail fast when no outbound network connectivity. #2951

Closed
slack opened this issue May 14, 2018 · 0 comments · Fixed by #3083
Closed

Discuss: Fail fast when no outbound network connectivity. #2951

slack opened this issue May 14, 2018 · 0 comments · Fixed by #3083
Assignees
@jackfrancis @CecileRobertMichon

Comments

@slack
Copy link
Contributor

slack commented May 14, 2018

Is this an ISSUE or FEATURE REQUEST? (choose one): FEATURE

It would be nice, with custom networking configurations, to fail cluster provisioning as fast as possible so that we don't hit the longer timeouts. For instance:

  • Fail quickly if node hostnames do not resolve.
  • Fail quickly if external DNS does not work.
  • Fail quickly if outbound connectivity is not working: apt-get ...

Upper bound would be ~ 5 minutes of not working, before we attempt any other provisioning steps.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@jackfrancis jackfrancis

@CecileRobertMichon CecileRobertMichon

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Check outbount connection at the start of CSE CecileRobertMichon/acs-engine
3 participants
@slack @jackfrancis @CecileRobertMichon