在fedora server 23上运行kube-proxy panic：运行时错误：无效内存地址或零指针取消引用

Question

软呢帽：

[root@host3 vagrant]# cat /etc/os-release
NAME=Fedora
VERSION="23 (Twenty Three)"
ID=fedora
VERSION_ID=23
PRETTY_NAME="Fedora 23 (Twenty Three)"
ANSI_COLOR="0;34"
CPE_NAME="cpe:/o:fedoraproject:fedora:23"
HOME_URL="https://fedoraproject.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=23
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=23
PRIVACY_POLICY_URL=https://fedoraproject.org/wiki/Legal:PrivacyPolicy

库贝-代理版本：

[root@host3 vagrant]# kube-proxy --version=true
Kubernetes v1.1.2

[root@host3 vagrant]# kube-proxy --logtostderr=true --v=0 --master=http://host1:8080 --proxy-mode=userspace --cleanup-iptables=true
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xb code=0x1 addr=0xb1 pc=0x465e26]

goroutine 1 [running]:
k8s.io/kubernetes/cmd/kube-proxy/app.(*ProxyServer).Run(0xc2080d79d0, 0xc208046af0, 0x0, 0x5, 0x0, 0x0)

goroutine 7 [chan receive]:
github.com/golang/glog.(*loggingT).flushDaemon(0x12169e0)

/go/src/k8s.io/kubernetes/godeps/_workspace/src/github.com/golang/glog/glog.go:879+0x78由github.com/golang/glog.init创建·1/go/src/k8s.io/kubernetes/godeps/_workspace/src/github.com/golang/glog/glog.go:410+0x2a7

goroutine 17 [syscall, locked to thread]:
runtime.goexit()
    /usr/src/go/src/runtime/asm_amd64.s:2232 +0x1

goroutine 15 [chan receive]:
github.com/godbus/dbus.(*Conn).outWorker(0xc2080daa20)

/go/src/k8s.io/kubernetes/godeps/_workspace/src/github.com/godbus/dbus/conn.go:367+0x58由github.com/godbus/dbus/dbus创建。(*conn).auth/go/src/k8s.io/kubernetes/godeps/_workspace/src/github.com/godbus/dbus/auth.go:119+0xEA1

goroutine 12 [sleep]:
k8s.io/kubernetes/pkg/util.Until(0xda66f0, 0x12a05f200, 0xc20800a7e0)

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/pkg/util/util.go:127+0x98由k8s.io/kubernetes/pkg/util.initlogs/go/src/dockerized/go/src/k8s.html" target="_blank">io/kubernetes/pkg/util/logs.go:49+0xab

goroutine 14 [IO wait]:
net.(*pollDesc).Wait(0xc2080d6920, 0x72, 0x0, 0x0)
    /usr/src/go/src/net/fd_poll_runtime.go:84 +0x47
net.(*pollDesc).WaitRead(0xc2080d6920, 0x0, 0x0)
    /usr/src/go/src/net/fd_poll_runtime.go:89 +0x43
net.(*netFD).readMsg(0xc2080d68c0, 0xc2080e28c0, 0x10, 0x10, 0xc20816d220, 0x1000, 0x1000, 0xffffffffffffffff, 0x0, 0x0, ...)
    /usr/src/go/src/net/fd_unix.go:296 +0x54e
net.(*UnixConn).ReadMsgUnix(0xc20803a0f0, 0xc2080e28c0, 0x10, 0x10, 0xc20816d220, 0x1000, 0x1000, 0x0, 0xc2080e276c, 0x4, ...)
    /usr/src/go/src/net/unixsock_posix.go:147 +0x167
github.com/godbus/dbus.(*oobReader).Read(0xc20816d200, 0xc2080e28c0, 0x10, 0x10, 0xc20816d200, 0x0, 0x0)

/go/src/k8s.io/kubernetes/godeps/_workspace/src/github.com/godbus/dbus/transport_unix.go:21+0xC5 IO.readat至少(0x7F7EEAE0DF58，0xC20816D200，0xC2080E28C0，0x10，0x10，0x10，0x10，0x10，0x10，0x0，0x0)/usr/src/go/src/Io.go:298+0xF1 IO.）/usr/src/go/src/io/io.go:316+0x6d github.com/godbus/dbus.(*unixtransport).readmess(0xC2081250d0,0xC208112660,0xC208112660,0x0,godbus/dbus/conn.go:241+0x58由github.com/godbus/dbus.(*conn)创建。auth/go/src/k8s.io/kubernetes/godeps/_workspace/src/github.com/godbus/dbus/auth.go:118+0xe84

goroutine 16 [runnable]:
k8s.io/kubernetes/pkg/util/iptables.(*runner).dbusSignalHandler(0xc2080d6850, 0x7f7eeae0e028, 0xc20803a100)

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/pkg/util/iptables/iptables.go:525由k8s创建。io/kubernetes/pkg/util/iptables/iptables.(*runner).connecttofirewalld/go/src/dockerized/go/src/k8s.io/kubernetes/pkg/util/iptables.go:186+0x7a7

有人能帮我吗？

Answer 1

在1.1.2版本中使用--cleanup-iptables=true标志时，这看起来像是一个bug，因为在GCE节点上运行时，我可能会重现恐慌。我已经代表您创建了Kubernetes#18197，这个bug将在即将发布的1.1.3版本中得到修复。