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

weave launch failure can take a long time to detect #538

Closed
rade opened this issue Apr 10, 2015 · 0 comments
Closed

weave launch failure can take a long time to detect #538

rade opened this issue Apr 10, 2015 · 0 comments
Labels
bug
Milestone
0.10.0

Comments

@rade
Copy link
Member

rade commented Apr 10, 2015 

# time weave launch -invalid_option
Container weave died

real    1m7.962s
user    0m0.023s
sys 0m0.006s

This was introduced in #509 and is a race... if the weave container dies before/during network configuration, then our script will catch that, but if it dies later then curl gets stuck attempting to connect to the status url.
@rade rade added the bug label Apr 10, 2015
@rade rade closed this as completed in 0799d9f Apr 10, 2015
@rade rade modified the milestone: 0.10.0 Apr 18, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
0.10.0
Development

No branches or pull requests
1 participant
@rade