Bug 1920509

Summary: wait for port 6443 to be open in the kube-scheduler container; use ss instead of lsof
Product: OpenShift Container Platform Reporter: Jan Chaloupka <jchaloup>
Component: kube-schedulerAssignee: Jan Chaloupka <jchaloup>
Status: CLOSED ERRATA QA Contact: RamaKasturi <knarra>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.7CC: aos-bugs, mfojtik
Target Milestone: ---   
Target Release: 4.7.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-02-24 15:56:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Jan Chaloupka 2021-01-26 12:41:49 UTC
"ss" shows sockets in CLOSE-WAIT state, so it's more accurate.

Comment 2 RamaKasturi 2021-01-27 13:02:24 UTC
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.

Comment 5 errata-xmlrpc 2021-02-24 15:56:23 UTC
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.