Description of problem: Customer is upgrading to Openshift 3.6 and facing the issue that is documented here: https://github.com/openshift/origin-web-console/issues/1773 Customer is wondering why the issue persists, despite the fix having been merged. Has the fix for the issue been deployed in post 3.6 versions of Openshift? Version-Release number of selected component (if applicable): OpenShift Master: v3.6.173.0.117 Kubernetes Master: v1.6.1+5115d708d7 How reproducible: Every time Steps to Reproduce: Actual results: Expected results: Additional info:
We had to revert the original fix before 3.6 since it caused a worse regression: https://github.com/openshift/origin-web-console/pull/1811 The problem was fixed in 3.7 when we switched to xterm.js for our terminal: https://github.com/openshift/origin-web-console/pull/1869 Sorry for the confusion. Moving ON_QA to verify that the problem is fixed in 3.7.
checked this issue has been fixed. OpenShift Master: v3.7.51 Kubernetes Master: v1.7.6+a08f5eeb62
Closing as already fixed in 3.7.z. Please let me know if you have any concerns.