Project

General

Profile

Actions

action #105145

closed

osd-deployment pipelines fail because ContainersNotInitialized size:M

Added by livdywan over 2 years ago. Updated about 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Organisational
Target version:
Start date:
2022-01-20
Due date:
2022-02-11
% Done:

0%

Estimated time:

Description

Observation

osd-deployment failed with the same error:

Waiting for pod gitlab/runner-ydlpfvpg-project-3530-concurrent-0h2jfn to be running, status is Pending
Waiting for pod gitlab/runner-ydlpfvpg-project-3530-concurrent-0h2jfn to be running, status is Pending
    ContainersNotInitialized: "containers with incomplete status: [init-permissions]"
    ContainersNotReady: "containers with unready status: [build helper]"
Waiting for pod gitlab/runner-ydlpfvpg-project-3530-concurrent-0h2jfn to be running, status is Pending
    ContainersNotInitialized: "containers with incomplete status: [init-permissions]"
    ContainersNotReady: "containers with unready status: [build helper]"
[...]
Waiting for pod gitlab/runner-ydlpfvpg-project-3530-concurrent-0h2jfn to be running, status is Pending
908 ContainersNotInitialized: "containers with incomplete status: [init-permissions]"
909 ContainersNotReady: "containers with unready status: [build helper]"
911ERROR: Job failed (system failure): prepare environment: waiting for pod running: timed out waiting for pod to start. Check https://docs.gitlab.com/runner/shells/index.html#shell-profile-loading for more information

Acceptance criteria

  • AC1: osd-deployment pipeline doesn't alert about internal gitlab k8s busy loops
  • AC2: osd-deployment pipelines automatically restart on known internal errors

Suggestions


Related issues 1 (0 open1 closed)

Copied from openQA Project - action #103527: osd-deployment pipelines fail and alerts are not handled size:MResolvedokurz

Actions
Actions

Also available in: Atom PDF