Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

kubernetes 1.11.0 kube-proxy error #65611

Closed
jicki opened this issue Jun 29, 2018 · 5 comments
Closed

kubernetes 1.11.0 kube-proxy error #65611

jicki opened this issue Jun 29, 2018 · 5 comments
Assignees
Labels
area/ipvs area/kube-proxy sig/node Categorizes an issue or PR as relevant to SIG Node.

Comments

@jicki
Copy link

jicki commented Jun 29, 2018

kubernetes version 1.11.0

CentOS Linux release 7.4.1708 (Core) 


[root@kubernetes-65 ~]# uname -a
Linux kubernetes-65 4.4.111-1.el7.elrepo.x86_64 #1 SMP Wed Jan 10 13:12:02 EST 2018 x86_64 x86_64 x86_64 GNU/Linux


[root@kubernetes-65 ~]# rpm -qa|grep ipset
ipset-libs-6.29-1.el7.x86_64
ipset-6.29-1.el7.x86_64

  • kube-proxy run error logs

6月 29 11:51:47 kubernetes-65 kube-proxy[73946]: E0629 11:51:47.439385   73946 ipset.go:156] Failed to make sure ip set: &{{KUBE-LOAD-BALANCER-SOURCE-IP hash:ip,port,ip inet 1024 65536 0-65535 Kubernetes service load balancer ip + port + source IP for packet filter purpose} map[] 0xc4203b6420} exist, error: error creating ipset KUBE-LOAD-BALANCER-SOURCE-IP, error: exit status 1
6月 29 11:51:52 kubernetes-65 kube-proxy[73946]: E0629 11:51:52.323873   73946 ipset.go:156] Failed to make sure ip set: &{{KUBE-EXTERNAL-IP hash:ip,port inet 1024 65536 0-65535 Kubernetes service external ip + port for masquerade and filter purpose} map[] 0xc4203b6420} exist, error: error creating ipset KUBE-EXTERNAL-IP, error: exit status 1
6月 29 11:51:57 kubernetes-65 kube-proxy[73946]: E0629 11:51:57.348685   73946 ipset.go:156] Failed to make sure ip set: &{{KUBE-LOAD-BALANCER hash:ip,port inet 1024 65536 0-65535 Kubernetes service lb portal} map[] 0xc4203b6420} exist, error: error creating ipset KUBE-LOAD-BALANCER, error: exit status 1
6月 29 11:52:02 kubernetes-65 kube-proxy[73946]: E0629 11:52:02.372216   73946 ipset.go:156] Failed to make sure ip set: &{{KUBE-LOOP-BACK hash:ip,port,ip inet 1024 65536 0-65535 Kubernetes endpoints dst ip:port, source ip for solving hairpin purpose} map[] 0xc4203b6420} exist, error: error creating ipset KUBE-LOOP-BACK, error: exit status 1
6月 29 11:52:07 kubernetes-65 kube-proxy[73946]: E0629 11:52:07.397256   73946 ipset.go:156] Failed to make sure ip set: &{{KUBE-LOOP-BACK hash:ip,port,ip inet 1024 65536 0-65535 Kubernetes endpoints dst ip:port, source ip for solving hairpin purpose} map[] 0xc4203b6420} exist, error: error creating ipset KUBE-LOOP-BACK, error: exit status 1


@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Jun 29, 2018
@jicki
Copy link
Author

jicki commented Jun 29, 2018

/sig node
/area ipvs
/area kube-proxy

@k8s-ci-robot k8s-ci-robot added sig/node Categorizes an issue or PR as relevant to SIG Node. area/ipvs area/kube-proxy and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Jun 29, 2018
@liggitt
Copy link
Member

liggitt commented Jun 29, 2018

duplicate of #65461?

@stewart-yu
Copy link
Contributor

Thanks for your error catch. @jicki
Please open the issuse with template, which convenience to others make choice about bug or not? thanks

@jicki
Copy link
Author

jicki commented Jun 29, 2018

@liggitt

I test to #65461

[root@kubernetes-65 ~]# ipset create foo hash:ip comment
ipset v6.29: Set cannot be created: set with the same name already exists


[root@kubernetes-65 ~]# ipset list foo
Name: foo
Type: hash:ip
Revision: 4
Header: family inet hashsize 1024 maxelem 65536 comment
Size in memory: 128
References: 0
Members:

@m1093782566
Copy link
Contributor

/close

It's fixed by #65533

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ipvs area/kube-proxy sig/node Categorizes an issue or PR as relevant to SIG Node.
Projects
None yet
Development

No branches or pull requests

5 participants