-
Bug
-
Resolution: Unresolved
-
Critical
-
3.19.0.GA, 3.20.0.GA
-
None
-
False
-
-
False
-
Release Notes
-
-
Known Issue
-
Done
-
Workaround Exists
-
-
-
Description of problem:
Workaround: restart workspace.
Prerequisites (if any, like setup, operators/versions):
Steps to Reproduce
- Install Dev Spaces 3.20.0.RC-1 (or Dev Spaces 3.19.0.GA) on OCP 4.18.5.
- Go to User Dashboard and create workspace using JBoss EAP 8.0 sample or another sample.
Actual results:
Workspace failed to start because of error:
Error creating DevWorkspace deployment: Container tools has state ImagePullBackOff
There was next error in the workspace events tab:
Failed to pull image "registry.redhat.io/devspaces/udi-rhel9@sha256:c4a47510e19bba187767225b23ee7fcad73b93e579a3a88b088027fd5c8f7797": rpc error: code = Canceled desc = copying system image from manifest list: copying config: context canceled
Pworkspace31a04a03bb9e4e17-57557859b-fzwnj
Generated from kubelet on ocp418-6xz4h-worker-0-bw7dc
08:04:32
Error: ErrImagePull
Expected results:
Workspace started successfully.
Reproducibility (Always/Intermittent/Only Once):
Intermittent
Acceptance criteria:
Definition of Done:
Build Details:
Additional info (Such as Logs, Screenshots, etc):
The error was reproduced
- on OCP 4.18.0 cluster which was using already released Dev Spaces 3.19.0 images from registry.redhat.io without any image mirroring.
- on DevSandbox stage cluster OCP 4.18.4 with Dev Spaces 3.20.0.RC-2 when start sample workspace using VS Code Editor and with Dev Spaces 3.20.0.RC-21 when start sample workspace using JetBrains IntelliJ IDEA (desktop) editor
- when start workspace using SSH Git URL of gogs private repository in Dev Spaces 3.20.0.RC-12 on pulling quay.io/devfile/universal-developer-image:ubi8-latest image:
On IBM Power there were few occurrences of this issue in the first release candidates, but tests which are using Git URL to start workspace were failing because if this error from time to time even in the latest release candidates on OCP 4.18 deployed to PSI.
On IBM Z there was no such an error on the different infra - IBM Z LPAR.