Skip to content

Error cleaning up configmap: resource name may not be empty

Summary

 Running with gitlab-runner 14.2.0 (58ba2b95)
   on Kubernetes Runner vXpkH225
Preparing the "kubernetes" executor
00:00
 Using Kubernetes namespace: gitlab
 Using Kubernetes executor with image <HOSTNAME>:9000/build:latest ...
 Using attach strategy to execute scripts...
Preparing environment
00:00
 ERROR: Error cleaning up configmap: resource name may not be empty
 ERROR: Job failed (system failure): prepare environment: setting up build pod: error setting ownerReferences: configmaps "runner-vxpkh225-project-42-concurrent-0-scriptsx5qf9" is forbidden: User "system:serviceaccount:gitlab:gitlab" cannot update resource "configmaps" in API group "" in the namespace "gitlab". Check https://docs.gitlab.com/runner/shells/index.html#shell-profile-loading for more information

Steps to reproduce

Running under gitlab-ee:12.10.12-ee.0 in docker, gitlab-runner managed by kubernetes 1.13 Affecting all projects, all pipelines.

.gitlab-ci.yml

.gitlab-ci.yml appears irrelevant - it's not getting that far.

Actual behavior

See above in Summary

Expected behavior

Should not fail :-)

Relevant logs and/or screenshots

job log

See summary above

Environment description

config.toml contents
concurrent = 4

[[runners]]
name = "Kubernetes Runner"
url =
    "https://<HOSTNAME>/gitlab/"
token = "<TOKEN>"
executor
    = "kubernetes"
environment=[\"GIT_SSL_NO_VERIFY=true\"]
output_limit=
    81280


[runners.kubernetes]
namespace = "gitlab"
image= "busybox"
image_pull_secrets
    = ["regcred"]
privileged=true

Used GitLab Runner version

All versions up to v14.1.0 work fine All versions since v14.2.0 fail

Version directly pulled as gitlab/gitlab-runner:v14.1.0, etc from docker

Possible fixes

Downgrade from latest to v14.1 in my kubernetes deployment has reverted to known working version. No fix known for broken versions.

Edited by KrayzeeKev