openpitrix 有一个pod始终起不来

mars

openpitrix-system其他的pod都正常，job也都已经正常执行完了，只有这一个有问题

 kubectl -n openpitrix-system logs openpitrix-iam-service-deployment-864df9fb6f-8v4qn
2019-10-31 10:58:58.05184 -INFO- Release OpVersion: [v0.3.5] (grpc_server.go:79)
2019-10-31 10:58:58.05187 -INFO- Git Commit Hash: [9333eae7354fc6634785df7a2fef35e74ed8dce5] (grpc_server.go:79)
2019-10-31 10:58:58.05189 -INFO- Build Time: [2018-11-22 06:37:13] (grpc_server.go:79)
2019-10-31 10:58:58.0519  -INFO- Service [iam-service] start listen at port [9115] (grpc_server.go:81)
2019-10-31 10:58:58.05456 -INFO- Init IAM client [5z1rfvnQx9OIXMUINPYUBZJ8U] done (init.go:39)
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x94ceb7]

goroutine 41 [running]:
openpitrix.io/openpitrix/vendor/github.com/sony/sonyflake.(*Sonyflake).NextID(0x0, 0x0, 0x0, 0x0)
        /go/src/openpitrix.io/openpitrix/vendor/github.com/sony/sonyflake/sonyflake.go:89 +0x37
openpitrix.io/openpitrix/pkg/util/idutil.GetIntId(0xc00035c000)
        /go/src/openpitrix.io/openpitrix/pkg/util/idutil/id.go:45 +0x2d
openpitrix.io/openpitrix/pkg/util/idutil.GetUuid(0xc5502b, 0x4, 0x0, 0x3c)
        /go/src/openpitrix.io/openpitrix/pkg/util/idutil/id.go:54 +0x29
openpitrix.io/openpitrix/pkg/models.NewUserId(0xc000398700, 0x0)
        /go/src/openpitrix.io/openpitrix/pkg/models/user.go:18 +0x36
openpitrix.io/openpitrix/pkg/models.NewUser(0xc000038137, 0x5, 0xc0001f2100, 0x3c, 0xc000038137, 0xc, 0xc5bab9, 0xc, 0x0, 0x0, ...)
        /go/src/openpitrix.io/openpitrix/pkg/models/user.go:39 +0x26
openpitrix.io/openpitrix/pkg/service/iam.initIAMAccount()
        /go/src/openpitrix.io/openpitrix/pkg/service/iam/init.go:61 +0x3dc
created by openpitrix.io/openpitrix/pkg/service/iam.Serve
        /go/src/openpitrix.io/openpitrix/pkg/service/iam/server.go:25 +0x5f

zheng1

你好, 如果pod的ip不是一个标准的内网ip, 如 192.168/16 或者 10/8 或者 172.16/12 的话, 需要给所有openpitrix的Deployment加上env OPENPITRIX_ID_RANDOM_SEED=yes

mars

zheng1 感谢。问题解决了

kevendeng

mars

fukang0611 E0914 10:38:13.965462 1 reflector.go:127] k8s.io/client-go/informers/factory.go:134: Failed to watch *v1.ReplicationController: failed to list *v1.ReplicationController: Get “https://172.22.151.165:6443/api/v1/replicationcontrollers?limit=500&resourceVersion=0”: dial tcp 172.22.151.165:6443: connect: connection refused

这些错误是因为kube-apiserver还没有启动完成并开始监听端口，kube-scheduler连接kube-apiserver失败。

fukang0611 E0914 10:38:30.519069 1 reflector.go:127] k8s.io/apiserver/pkg/server/dynamiccertificates/configmap_cafile_content.go:206: Failed to watch *v1.ConfigMap: failed to list *v1.ConfigMap: configmaps “extension-apiserver-authentication” is forbidden: User “system:kube-scheduler” cannot list resource “configmaps” in API group "" in the namespace “kube-system”

这些错误是因为kube-apiserver还没有初始化完成本地鉴权所需的数据，kube-scheduler的请求因为权限不足失败。

在这之后，kube-scheduler应该已经正常运行了。