locksmithcl: reset endpoints
when we set a new one
#13
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This behavior was working fine previously but no more with the etcd/v2
upgrade.
In the case we have an endpoint like
https://127.0.0.1:2379
, this onewill be added to the list of
defaultEndpoints
which lead to thisendpoints:
It's not an issue when we have a retry mechanism - but in this case if
etcd
use HTTPS and we try anHTTP
endpoint, we will get an io.EOFerror.
Signed-off-by: Mathieu Tortuyaux mathieu@kinvolk.io
Otherwise, we could just do this:
but, as a user, I would expect that if I run
locksmithctl -endpoint https://127.0.0.1:2379
I would run locksmithcl only against this endpoint, not a bundle ofdefautEndpoints + endpoint
.This issue has been caught by the CI with the
coreos.locksmith.tls
- I will rerun the kola tests before merging this one.