[1149244511] Upstream Reporter: Johannes 'fish' Ziemke
Upstream issue status: Closed
Upstream description:

Looks like at least when doing exec, conmon is ignoring the exit status of the runtime and returns 0. That made it really hard to pin point an issue we're having.

Using /bin/false to easily reproduce:

# conmon -c <id> -n /runtime.v1alpha2.RuntimeService/Exec -p /mnt/crio/overlay-containers/<id>/userdata/pidfile -e --socket-dir-path /var/run/crio --exec-process-spec exec-spec.json -r /bin/false --log-path /dev/stdout
# echo $?
0