ip: address and route output formatting differs from oracle

[matt-dz]

Summary

rshell and the oracle produced different pwd pwd; uname -a; ip addr; ip route results.

Command

pwd; uname -a; ip addr; ip route

Reduced command shape: pwd; uname -a; ip addr; ip route

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
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0@if5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether 4a:17:21:5a:3d:31 brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet 172.18.0.2/16 brd 172.18.255.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fc00:f853:ccd:e793::2/64 scope global nodad 
       valid_lft forever preferred_lft forever
    inet6 fe80::4817:21ff:fe5a:3d31/64 scope link 
       valid_lft forever preferred_lft forever
3: veth8c03d53d@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether c6:e1:8d:eb:62:ce brd ff:ff:ff:ff:ff:ff link-netns cni-324a34f4-9705-0bcb-f4a6-fdb1d92d6a3a
    inet 10.244.0.1/32 scope global veth8c03d53d
       valid_lft fo
... <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
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP group default qlen 1000
    link/ether 4a:17:21:5a:3d:31 brd ff:ff:ff:ff:ff:ff
    inet 172.18.0.2/16 brd 172.18.255.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fc00:f853:ccd:e793::2/64 scope global
       valid_lft forever preferred_lft forever
    inet6 fe80::4817:21ff:fe5a:3d31/64 scope link
       valid_lft forever preferred_lft forever
3: veth8c03d53d: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP group default qlen 1000
    link/ether c6:e1:8d:eb:62:ce brd ff:ff:ff:ff:ff:ff
    inet 10.244.0.1/32 brd 10.244.0.1 scope global veth8c03d53d
       valid_lft forever preferred_lft forever
    inet6 fe80::c4e1:8dff:feeb:62ce/64 scope link
       valid_lft forever preferred
... <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-20260603T153137.298240572Z-c2274bb3
• Observed invocations: 1
• Scenario count: 1
• Differing dimension: stdout
• Behavior cluster: pwd-unexpected-stdout:pwd; uname -a; ip addr; ip route

[matt-dz]

QA triage correction: this was originally filed under pwd, but the meaningful non-uname diff is from ip addr / ip route output formatting. The uname -a stdout delta is tracked separately in #522.