"ss" shows sockets in CLOSE-WAIT state, so it's more accurate.
Verified bug in the payload below and i see that changes present in the PR are present. [knarra@knarra ~]$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.7.0-0.nightly-2021-01-27-022930 True False 175m Cluster version is 4.7.0-0.nightly-2021-01-27-022930 Before the fix: ================= [knarra@knarra ~]$ oc get pod openshift-kube-scheduler-wduan-0126b-xtdcv-control-plane-0 -o yaml -n openshift-kube-scheduler | grep 10251 port: 10251 port: 10251 echo -n "Waiting for port :10259 and :10251 to be released." while [ -n "$(lsof -ni :10251)" -o -n "$(lsof -i :10259)" ]; do After the fix: =================== [knarra@knarra ~]$ oc get pod openshift-kube-scheduler-ip-10-0-147-38.us-east-2.compute.internal -o yaml -n openshift-kube-scheduler | grep 10251 echo -n "Waiting for port :10259 and :10251 to be released." while [ -n "$(ss -Htan '( sport = 10251 or sport = 10259 )')" ]; do Based on the above moving bug to verified state.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:5633