Description of problem:
$ curl -s https://storage.googleapis.com/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-4.0/6581/artifacts/e2e-aws/pods/openshift-kube-scheduler_openshift-kube-scheduler-ip-10-0-134-174.ec2.internal_scheduler_previous.log.gz | gunzip | tail -n1
failed to create listener: failed to listen on 0.0.0.0:10251: listen tcp 0.0.0.0:10251: bind: address already in use
Just like bug 1691055, but for a different operator.
Version-Release number of selected component (if applicable):
$ curl -s https://storage.googleapis.com/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-4.0/6581/artifacts/release-images-latest/release-images-latest | jq -r '.spec.tags | select(.name == "cluster-kube-scheduler-operator").annotations'
Created attachment 1553955 [details]
Occurrences of this error in CI from 2019-04-08T21:15 to 2019-04-09T20:50 UTC
This occurred in 36 of our 355 failures (10%) in *-e2e-aws* jobs across the whole CI system over the past 23 hours. Generated with :
$ deck-build-log-plot 'kube-scheduler.*listen tcp 0.0.0.0:10251: bind: address already in use'
Maciej has a fix in Trevor's linked bug ... might be a similar fix here?
kube-controller-manager-operator addresses this with an init container that waits on the port to open up
Ravi, already has a PR open
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, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.