Project

General

Profile

action #128669

Updated by okurz over 1 year ago

## Observation 
 From https://gitlab.suse.de/openqa/openqa-review/-/jobs/1550012 

 ``` 
 Running with gitlab-runner 15.11.0 (436955cb) 
   on gitlab-worker4:sle15.3 sHAdmiLV, system ID: s_d2d8982b55c6 
 Preparing the "docker" executor 00:21 
 ERROR: Failed to remove network for build 
 ERROR: Preparation failed: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? (docker.go:780:12s) 
 Will be retried in 3s ... 
 ERROR: Failed to remove network for build 
 ERROR: Preparation failed: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? (docker.go:780:0s) 
 Will be retried in 3s ... 
 ERROR: Failed to remove network for build 
 ERROR: Preparation failed: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? (docker.go:780:0s) 
 Will be retried in 3s ... 
 ERROR: Job failed (system failure): Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? (docker.go:780:0s) 
 ``` 

 ## Steps to reproduce 

 Might be runner specific, reproduced in https://gitlab.suse.de/openqa/openqa-review/-/jobs/1550017, same runner id. So far not reproduced on other runners. 

 ## Workaround 
 Likely a manual retriggering will work if a different worker is found 

 
 ## Expected result 
 Pipeline owners should not be concerned with runner problems but only runner admins should be notified. 

 ## Impact 
 Scheduling, monitoring and reporting of SLE product validation and SLE maintenance update testing is impacted and needs manual handling of failed pipeline jobs causing misses and delays.

Back