ping is not a good check to test the connection to the CDN #19
Comments
m8ram
added a commit
to m8ram/sat6_healthCheck
that referenced
this issue
Feb 10, 2016
Use curl instead of ping to test the connection to the CDN. Use a proxy if one is configured in the katello answer file.
|
I second the motion to please test connectivity with curl instead of ping (ping will fail at > 75% of the customers I get sent to). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The connection to the CDN is tested with ping. This causes false negatives and may even cause a false positive.
This is because our satellite needs to connect through a proxy. Not only is the satellite system itself unable to resolve the URI, even it were able to ping would not work this way.
Also a ping test does not guarantee that other connections can be made and/or ping can be blocked independently without blocking the required connections.
Is there a different way to test this? Perhaps using wget/curl and using the proxy as defined in the satellite's config?
The text was updated successfully, but these errors were encountered: