awslabs/benchmark-ai

[Watcher] Init:ImagePullBackOff - bad status

Open

#843 opened on Sep 12, 2019

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Python (6 forks)auto 404
buggood first issuep1service:watcher

Repository metrics

Stars
 (19 stars)
PR merge metrics
 (PR metrics pending)

Description

The benchmark pod could not start due to an error pulling the image:

Events:
  Type     Reason   Age                      From                                                 Message
  ----     ------   ----                     ----                                                 -------
  Warning  Failed   12m (x11600 over 44h)    kubelet, ip-172-16-3-152.eu-west-1.compute.internal  Error: ImagePullBackOff
  Normal   BackOff  2m26s (x11643 over 44h)  kubelet, ip-172-16-3-152.eu-west-1.compute.internal  Back-off pulling image "benchmarkai/puller:00dd240"

The watcher is interpreting it as pending initialization - we should probably update this to some error state, ask the user to --cancel the job (or issue a cancel cmd) and stop the watcher for that job.

👀 |872094df|Job is pending initialization
👀 |96f36526|Job is pending initialization
👀 |8aa5afad|Job is pending initialization
👀 |0166c689|Job is pending initialization
👀 |30ea029f|Job is pending initialization
👀 |9e5ad88c|Job is pending initialization
👀 |aaa76525|Job is pending initialization
👀 |5e0d6099|Job is pending initialization
👀 |0fdf7b9c|Job is pending initialization
👀 |608ba177|Job is pending initialization
👀 |d15f2415|Job is pending initialization
👀 |368f7697|Job is pending initialization
👀 |20f9ddd5|Job is pending initialization
👀 |63c2bffb|Job is pending initialization
👀 |1ff3627d|Job is pending initialization
....

Contributor guide

Research direction
Examine the watcher's status polling logic and add detection for 'ImagePullBackOff' error. Update the status message to indicate an error state and provide instructions for the user to cancel the job.
Tech stack
python
Domain
backenddevops
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
PythonKubernetesGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65