Hide Forgot
Description of problem: Use oc rsh to login to the pod, and leave the session there till it gets timeout. Login the pod again to check the running processes. The old processes for the previous timeout session are still there. They should be cleaned up automatically once the session closed. Version-Release number of selected component (if applicable): oc v3.3.1.1 kubernetes v1.3.0+52492b4 How reproducible: always Steps to Reproduce: 1. Create a pod in the running cluster 2. Login to the pod via oc rsh 3. Wait for the session above timeout and exit 4. Login the pod again via oc rsh 5. Check the running processes. Actual results: The old processes still exist. Expected results: Should clean up the processes once the session closed. Additional info: sh-4.2$ echo $$ 446 sh-4.2$ ps -ef UID PID PPID C STIME TTY TIME CMD 1000020+ 1 0 0 Oct09 ? 00:00:13 /usr/bin/openshift-router 1000020+ 254 0 0 Oct09 ? 00:00:00 /bin/sh 1000020+ 281 1 0 Oct09 ? 00:00:39 /usr/sbin/haproxy -f /var/lib/haproxy/conf/haproxy.config -p /var/lib/haproxy/run/haproxy.pid -sf 248 1000020+ 294 0 0 Oct09 ? 00:00:00 /bin/sh 1000020+ 338 0 0 01:19 ? 00:00:00 /bin/sh 1000020+ 352 338 0 01:20 ? 00:00:03 top 1000020+ 375 0 0 01:21 ? 00:00:00 /bin/sh 1000020+ 392 0 0 02:30 ? 00:00:00 /bin/sh 1000020+ 426 0 0 02:44 ? 00:00:00 bash 1000020+ 445 426 0 02:44 ? 00:00:00 sleep 99999 1000020+ 446 0 0 05:19 ? 00:00:00 /bin/sh 1000020+ 452 446 0 05:40 ? 00:00:00 ps -ef
This BZ has no customer issue attached, is for OCP 3.3, and is low severity. Closing as wontfix. If this remains an issue or becomes higher priority, please re-open.