[sig-cli] Kubectl client Simple pod should support inline execution and attach fails

[saschagrunert]

Which jobs are failing?

CRI-O conmonrs e2e feature tests.

Which tests are failing?

Mentioned in the title, ran via: https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/cri-o_cri-o/6220/pull-ci-cri-o-cri-o-main-ci-e2e-conmonrs/1572188830188965888

Since when has it been failing?

Since ever, reproducible with 8e4cec9

Reason for failure (if possible)

I guess it’s something in the attach stdin code.

Anything else we need to know?

No response

[saschagrunert]

#746 partly adresses this one.

The --leave-stdin-open=true tests are still failing: https://github.com/kubernetes/kubernetes/blob/7f129f1c9af62cc3cd4f6b754dacdf5932f39d5c/test/e2e/kubectl/kubectl.go#L614-L648

[saschagrunert]

Latest run: https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/cri-o_cri-o/6220/pull-ci-cri-o-cri-o-main-ci-e2e-conmonrs/1572942729908850688