ps: `ps -ef` output formatting differs from oracle

Open
#520 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
go, linux, shell

Research direction

The issue names no source file or test. Start by reproducing the reduced command and compare the uname -a and ps -ef output with the oracle; trace the rshell command path responsible for ps formatting. Done means the command exits 0 with matching stdout and empty stderr for the reported scenario.

Written by the indexing model from the issue text.

Description

QA

Summary

rshell and the oracle produced different pwd pwd; uname -a; ps -ef | grep -E "kubelet|containerd|elasticsearch|kafka|mezmo" | grep -v grep results.

Command

pwd; uname -a; ps -ef | grep -E "kubelet|containerd|elasticsearch|kafka|mezmo" | grep -v grep

Reduced command shape: pwd; uname -a; ps -ef | grep -E "kubelet|containerd|elasticsearch|kafka|mezmo" | grep -v grep

Expected (oracle)

Exit code: 0

stdout:

/
Linux pshim-control-plane 6.17.0-1016-gcp #17~24.04.1-Ubuntu SMP Fri May  8 07:28:18 UTC 2026 aarch64 GNU/Linux
root         165       1  2 15:25 ?        00:02:51 /usr/local/bin/containerd
root         291       1  0 15:25 ?        00:00:01 /usr/local/bin/containerd-shim-runc-v2 -namespace k8s.io -id 3fe44819fb201156dceeeb97fa817430d9b765cfe73b649a0fa9dd8c296e930e -address /run/containerd/containerd.sock
root         292       1  0 15:25 ?        00:00:01 /usr/local/bin/containerd-shim-runc-v2 -namespace k8s.io -id 1cadb0ba5c4bbafcbfd19ee25703a165124c54d0a087e0bbab4ace41683f0c42 -address /run/containerd/containerd.sock
root         296       1  0 15:25 ?        00:00:01 /usr/local/bin/containerd-shim-runc-v2 -namespace k8s.io -id 3b700e0b4fc593b09fc468830f52a31cc550271d69c9eaa1e498372ae044f129 -address /run/containerd/containerd.sock
root         330       1  0 15:25 ?        00:00:01 /usr/local/bin/containerd-shim-runc-v2 -namespace k8s.io -id 871747464f9747f2940df11a6ce7f1163e470c05dbe05ff21b54f2975530b26c -address /run/containerd/containerd.sock
root         597     296  3 15:25 ?        00:03:37 kube-apiserver --advertise-address=172.18.0.2 --allow-privil
... <truncated>

stderr:

(empty)

Actual (rshell)

Exit code: 0

stdout:

/
Linux pshim-control-plane 6.17.0-1016-gcp #17~24.04.1-Ubuntu SMP Fri May  8 07:28:18 UTC 2026 aarch64
0              1275      1  0 15:25 ?            00:00:01 containerd-shim
0              1307      1  0 15:25 ?            00:00:01 containerd-shim
0               165      1  0 15:25 ?            00:02:51 containerd
0               291      1  0 15:25 ?            00:00:01 containerd-shim
0               292      1  0 15:25 ?            00:00:01 containerd-shim
0               296      1  0 15:25 ?            00:00:01 containerd-shim
0               330      1  0 15:25 ?            00:00:01 containerd-shim
0              3320      1  0 15:25 ?            00:00:01 containerd-shim
0              3338      1  0 15:25 ?            00:00:01 containerd-shim
0              3355      1  0 15:25 ?            00:00:01 containerd-shim
0             44475      1  0 17:12 ?            00:00:00 containerd-shim
0             44556      1  0 17:12 ?            00:00:00 containerd-shim
0             44607      1  0 17:12 ?            00:00:00 containerd-shim
0             44622      1  0 17:12 ?            00:00:00 containerd-shim
0             45253      1  0 17:12 ?
... <truncated>

stderr:

(empty)

Why This Matters

The QA run observed this command shape in 1 invocation across 1 scenario.

QA provenance
  • QA run id: run-20260603t152010z-pwd
  • Target builtin: pwd
  • Rshell commit/version: unknown
  • Example invocation: inv-20260603T172400.297507151Z-7235e057
  • Observed invocations: 1
  • Scenario count: 1
  • Differing dimension: stdout
  • Behavior cluster: pwd-unexpected-stdout:pwd; uname -a; ps -ef | grep -E "kubelet|containerd|elasticsearch|kafka|mezmo" | grep -v grep
Dominant language
Go
Stars
31
Forks
3
Avg merge
1d 12h
Merged PRs (30d)
11

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.

More from DataDog/rshell

All issues in DataDog/rshell

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.