rstudio / rstudio/helm

Workbench diagnostics.enabled fails by default if enabled

Open
#460 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

team: workbench
Dominant language
Markdown
Stars
46
Forks
40
Avg merge
4h 3m
Merged PRs (30d)
6

Description

Setting diagnostics.enabled: true produces a segfault error in the pod logs:

2024-01-31T13:40:58.692978Z [rserver] INFO Server: RStudio - stats monitor reporting interval: 60s
Job launcher configured with the following clusters: Kubernetes
launcher-adhoc-clusters is empty - all clusters may be used to launch adhoc jobs
launcher-sessions-clusters is empty - all clusters may be used to launch session jobs
Cluster Kubernetes does not have any session images explicitly configured in  /mnt/configmap/rstudio/rserver.conf or launcher-sessions-container-image config settings. Skipping launch of test job since we do not know which images we can use
/usr/sbin/rstudio-server: line 25:  1160 Segmentation fault      /usr/lib/rstudio-server/bin/rserver --verify-installation=1 --server-daemonize=0 $1 $2 $3 $4 $5 $6 $7 $8
Checking Job Launcher configuration... Ensuring server-user is a Job Launcher admin... Getting list of Job Launcher clusters... Job launcher configured with the following clusters: Kubernetes launcher-adhoc-clusters is empty - all clusters may be used to launch adhoc jobs launcher-sessions-clusters is empty - all clusters may be used to launch session jobs Cluster Kubernetes does not have any session images explicitly configured in /mnt/configmap/rstudio/rserver.conf or launcher-sessions-container-image config settings. Skipping launch of test job since we do not know which images we can use
Exiting script because DIAGNOSTIC_ONLY=true

Setting launcher-sessions-container-image explicitly in rserver.conf allows it to run. However Jupyter and VS Code are skipped unless session-container-images is listed in jupyter.conf and vscode.conf

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing how diagnostics.enabled is translated into rserver.conf, especially launcher-sessions-container-image, then compare the related session-container-images settings in jupyter.conf and vscode.conf. Reproduce with diagnostics.enabled: true and verify that the pod does not segfault and that Jupyter and VS Code are not skipped without extra configuration.

Written by the indexing model from the issue text.

Assessment

Tech stack
helm, jupyter, kubernetes, vscode
Domain
devops, infrastructure
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.