Execute cells FAILED on Kubernetes pod
See original GitHub issueIssue Type: Bug
When running a cell in an existing notebook (i.e. one that is saved somewhere) on a Kubernetes pod, the cell does not execute. The following is logged to Remote Extension Host:
[2021-06-29 04:51:14.316] [exthost] [error] NotebookController[1] execute cells FAILED {}
Furthermore, the output in developer tools shows:
Error: duplicate execution for vscode-notebook-cell://k8s-container...
I can provide the full output if that would be helpful.
Note: In a fresh, unsaved notebook created using Jupyter: Create new blank notebook
, the cells execute without problem. The problem only manifests once the notebook is saved.
Steps to reproduce:
- Open VSCode on a Kubernetes pod
- Create a blank notebook
- Save the notebook to disk somewhere
- Attempt to run the first cell
Extension version: 2021.6.999662501 VS Code version: Code 1.57.1 (507ce72a4466fbb27b715c3722558bb15afa9f48, 2021-06-17T13:28:32.912Z) OS version: Darwin x64 20.5.0 Restricted Mode: No Remote OS version: Linux x64 5.4.89+
System Info
Item | Value |
---|---|
CPUs | Intel® Core™ i7-8850H CPU @ 2.60GHz (12 x 2600) |
GPU Status | 2d_canvas: enabled gpu_compositing: enabled metal: disabled_off multiple_raster_threads: enabled_on oop_rasterization: enabled opengl: enabled_on rasterization: enabled skia_renderer: disabled_off_ok video_decode: enabled webgl: enabled webgl2: enabled |
Load (avg) | 2, 2, 3 |
Memory (System) | 16.00GB (0.02GB free) |
Process Argv | –crash-reporter-id 3253bfa9-f4f2-4dc6-9afe-91a2465ce2f7 |
Screen Reader | no |
VM | 0% |
Item | Value |
---|---|
Remote | pod-sabri in pod-sabri (gcr.io/hai-gcp-fine-grained/default) |
OS | Linux x64 5.4.89+ |
CPUs | Intel® Xeon® CPU @ 2.20GHz (8 x 2199) |
Memory (System) | 29.40GB (12.80GB free) |
VM | 0% |
A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
pythonvspyt700cf:30270857
pythonvspyt602:30300191
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyt639:30300192
pythontb:30283811
pythonvspyt551cf:30311713
vspre833:30321513
pythonptprofiler:30281270
vshan820:30294714
pythondataviewer:30285071
vscus158:30321503
pythonvsuse255cf:30323309
vscorehov:30309549
vscod805cf:30301675
vscextlangct:30322307
binariesv615:30325510
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Determine the Reason for Pod Failure - Kubernetes
In the YAML file, in the command and args fields, you can see that the container sleeps for 10 seconds and then writes...
Read more >Getting error while running workflow on kubernetes · Issue #244
Issue 2: When I deploy the Kubeflow pipeline there is no error message but the pod for running to executing the pipeline is...
Read more >1615375 – Failed to create pod, due to CNI issues
Go to the node in question, find the docker process that is running ovs, and use docker exec. Do you know the general...
Read more >Creating a container fails in Tanzu Application Service or ...
The common error "Failed to get node vif or TN ID for node ..." means the NCP job fails to find the logical...
Read more >Run a container on a pod failure Kubernetes - Stack Overflow
There is nothing built in for this that i am aware of. You could use a web hook to get notified when a...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
There’s another issue with that sort of URI https://github.com/microsoft/vscode-remote-release/issues/5250. It’s possible that the weird URI format could cause an issue like this too. Sounds like it will be fixed in the Containers extension
Looks like this has been fixed with the most recent VS Code + Containers Extension release. Please ping here if you are still seeing it with everything updated.