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

Fix unexpected etcd image error if docker pulls images over proxy #226

Merged
merged 2 commits into from
Jul 29, 2019

Conversation

kirrmann
Copy link
Contributor

@kirrmann kirrmann commented Jul 2, 2019

I tried to use etcd-manager in kops which is setup to use a proxy to pull docker images.

spec:
  assets:
    containerProxy: nexus.internal:8500

But starting etcd-manager would always abort with error initializing etcd server: unexpected etcd image \“nexus.internal:8500/etcd:2.2.1\“

The two colons do incorrectly let a check fail to verify the specified name of the etcd docker image.

@kirrmann kirrmann force-pushed the patch-1 branch 2 times, most recently from 3345578 to a610152 Compare July 3, 2019 06:30
@kirrmann
Copy link
Contributor Author

kirrmann commented Jul 7, 2019

tests run fine locally. Seems like the travis builds just have time outs

@justinsb
Copy link
Contributor

Thanks @kirrmann - and I believe we've fixed those timeouts on head (but travis does not rebase before testing).

I tweaked the logic so that it would pick up the version even in the "3 component" case, but thanks for reporting & fixing!

/approve
/lgtm

@justinsb justinsb merged commit 3fcbb1a into kopeio:master Jul 29, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants