Troubleshoot workspace content
Find out why a workspace’s Arena run, project, skills or content path is not what you expected.
Prerequisites
Section titled “Prerequisites”kubectlaccess to the cluster.- A workspace with content storage. See Workspace content layout.
Troubleshooting
Section titled “Troubleshooting”A run used content you did not expect
Section titled “A run used content you did not expect”An Arena run tested files other than the ones you edited.
-
Read what the run resolved.
Terminal window kubectl get arenarun -n <namespace> <run> \-o jsonpath='{.status.source.ref} {.status.source.commit} {.status.source.contentPath}' -
Compare
commitwith the project’sstatus.repository.head, or with the commit you expected. A run executes a commit of the repository, never anyone’s clone, so an edit that was never pushed is the usual cause. A commit pushed after the run started is not picked up.
A project is missing from the projects list
Section titled “A project is missing from the projects list”A project’s files are on the volume but the dashboard does not list it.
The list is the ArenaProject objects in the workspace’s namespace, not a directory listing. Confirm the object exists, then read its phase and Ready condition.
kubectl get arenaproject -n <namespace>A project’s files differ between two people
Section titled “A project’s files differ between two people”Two users see different files in one project.
Each user edits their own clone and sees another’s edits only after they are pushed and the clone has caught up with the repository.
An agent has no skills
Section titled “An agent has no skills”An agent starts but loads no skills.
- Confirm the PromptPack declares
spec.skillsand the operator has a workspace content path. The chart always passes--workspace-content-path(default/workspace-content), so check the operator’s start-up log for “workspace content storage is disabled” if you changed its arguments. Without both, the agent pod does not mount the volume. - Read the PromptPack’s
SkillsResolved,SkillsValidandSkillToolsResolvedconditions. - Confirm
manifests/<promptpack>.jsonexists on the volume. The manifest write is best-effort, so healthy conditions do not guarantee a manifest.
A content path is missing its workspace prefix
Section titled “A content path is missing its workspace prefix”A path such as a pod’s subPath shows a {workspace}/{namespace} prefix in one cluster and not in another.
The prefix appears on a shared volume and not on a scoped one. See Workspace content layout.