Skip to content

Kubernetes executor panics when no referees are configured.

Overview

When using kubernetes executor there seems to be some kind of panic happening when the referees are not configured.

Checking for jobs... received                       job=956 repo_url=http://192.168.157.160:3000/root/playground.git runner=o5hBR1gQ
2019/12/17 10:39:39 concurrentID: ""
WARNING: Namespace is empty, therefore assuming 'default'.  job=956 project=19 runner=o5hBR1gQ
executor not supported                              job=956 project=19 referee=metrics runner=o5hBR1gQ
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x28 pc=0x148f170]

goroutine 204 [running]:
gitlab.com/gitlab-org/gitlab-runner/referees.(*MetricsReferee).Execute(0x0, 0x25f53c0, 0xc0004d0000, 0xbf764676de48c308, 0xaab3bd992, 0x312a680, 0xbf764676de8051b0, 0xaab736a8b, 0x312a680, 0x0, ...)
        /Users/steve/Code/gitlab.com/gitlab-org/gitlab-runner/referees/metrics_referee.go:59 +0x190
gitlab.com/gitlab-org/gitlab-runner/common.(*Build).executeUploadReferees(0xc000116380, 0x25f53c0, 0xc0004d0000, 0x2608640, 0xc000116700, 0xbf764676de48c308, 0xaab3bd992, 0x312a680, 0xbf764676de8051b0, 0xaab736a8b, ...)
        /Users/steve/Code/gitlab.com/gitlab-org/gitlab-runner/common/build.go:329 +0x199
gitlab.com/gitlab-org/gitlab-runner/common.(*Build).executeScript(0xc000116380, 0x25f53c0, 0xc0004d0000, 0x2608640, 0xc000116700, 0x0, 0x0)
        /Users/steve/Code/gitlab.com/gitlab-org/gitlab-runner/common/build.go:297 +0x222
gitlab.com/gitlab-org/gitlab-runner/common.(*Build).run.func1(0xc000470180, 0xc000116380, 0x25f53c0, 0xc0004d0000, 0x2608640, 0xc000116700)
        /Users/steve/Code/gitlab.com/gitlab-org/gitlab-runner/common/build.go:403 +0x56
created by gitlab.com/gitlab-org/gitlab-runner/common.(*Build).run
        /Users/steve/Code/gitlab.com/gitlab-org/gitlab-runner/common/build.go:402 +0x214
exit status 2