goldpinger UI fails if a node is in bad state. about goldpinger HOT 16 CLOSED

For more info, this is the case where ping would hang, instead of immediately returning error code. Will that be a possible reason why the UI just hangs and doesn't show?

from goldpinger.

This looks like a regression. Will try to reproduce and report back.

from goldpinger.

Could you paste a sample output from a call to /check_all ? That would help debugging. Thanks!

from goldpinger.

OK, I could reproduce the behaviour. Would you like to take #68 for a spin and confirm it works in your case?

from goldpinger.

@seeker89 thank you! will try it and let you know

from goldpinger.

@seeker89 unfortunately the problem persists. The behavior is a little different though:
instead of throwing weird error, it just hangs for some time and shows red dots:

from goldpinger.

/check_all would show this result after some time:

{"hosts":[{"hostIP":"10.120.252.11","podIP":"10.2.97.146"},{"hostIP":"10.120.252.13","podIP":"10.2.96.83"},{"hostIP":"10.120.252.12","podIP":"10.2.66.71"},{"hostIP":"10.120.252.10","podIP":"10.2.117.162"},{"hostIP":"10.120.252.14","podIP":"10.2.89.70"},{"hostIP":"10.120.252.15","podIP":"10.2.2.91"},{"hostIP":"10.120.252.18","podIP":"10.2.123.96"},{"hostIP":"10.120.252.17","podIP":"10.2.92.81"},{"hostIP":"10.120.252.16","podIP":"10.2.54.83"}],"responses":{"10.2.117.162":{"HostIP":"10.120.252.10","OK":false,"error":"Get http://10.2.117.162:80/check: context deadline exceeded"},"10.2.123.96":{"HostIP":"10.120.252.18","OK":false,"error":"Get http://10.2.123.96:80/check: context deadline exceeded"},"10.2.2.91":{"HostIP":"10.120.252.15","OK":false,"error":"Get http://10.2.2.91:80/check: context deadline exceeded"},"10.2.54.83":{"HostIP":"10.120.252.16","OK":false,"error":"Get http://10.2.54.83:80/check: context deadline exceeded"},"10.2.66.71":{"HostIP":"10.120.252.12","OK":false,"error":"Get http://10.2.66.71:80/check: context deadline exceeded"},"10.2.89.70":{"HostIP":"10.120.252.14","OK":false,"error":"Get http://10.2.89.70:80/check: context deadline exceeded"},"10.2.92.81":{"HostIP":"10.120.252.17","OK":false,"error":"Get http://10.2.92.81:80/check: context deadline exceeded"},"10.2.96.83":{"HostIP":"10.120.252.13","OK":false,"error":"Get http://10.2.96.83:80/check: context deadline exceeded"},"10.2.97.146":{"HostIP":"10.120.252.11","OK":false,"error":"Get http://10.2.97.146:80/check: context deadline exceeded"}}}

from goldpinger.

The behavior in safari is also different, as it throws error:

from goldpinger.

Ok. So it works properly if a pod is in bad state. (manually making a goldpinger pod in invalid state). However, if a node's networking is messed up (i.e. ping hangs, instead of returning error right away), then goldpinger UI would hang. You can easily reproduce it by stopping the underlying virtual machine.

from goldpinger.

Thanks for taking it for a spin. In that case we should tweak the logic displaying things, when there is not enough data. I should be able to sit down to it next week. Cheers!

from goldpinger.

@seeker89 thank you again for the quick response! I will look forward to the fix :)

from goldpinger.

@seeker89 did you get any chance to fix this issue? thank you

from goldpinger.

Sorry, haven't gotten to that yet.

from goldpinger.

Hi, any update on this? Maybe I can help. Haven't got any experience with this but why not learn.

from goldpinger.

@kristoflemmens that would be great and much appreciated. I haven't been able to find time since November!

from goldpinger.

Hi, any update?

from goldpinger.