+++ This bug was initially created as a clone of Bug #1852058 +++ +++ This bug was initially created as a clone of Bug #1852056 +++ Description of problem: Currently the etcd health check timeout inside kube-apiserver is hard coded to `2s`. This is very aggressive, change the timeout to 10s This should help the upgrade failures we are seeing in Azure - https://bugzilla.redhat.com/show_bug.cgi?id=1852047
Checked the PR which only has one change from 2 seconds to 10 seconds. No test action from QE. Thus could move to VERIFIED. Confirmed the PR has been landed to the latest OCP 4.4 payload, see below, $ oc adm release info --commits registry.svc.ci.openshift.org/ocp/release:4.4.0-0.nightly-2020-07-10-004502 |grep origin hyperkube https://github.com/openshift/origin b8568b30f485f5f37f0cdb14f803b629610248a2 $ git log --date local --pretty="%h %an %cd - %s" b8568b3 | grep '#25222' b8568b30f4 OpenShift Merge Robot Thu Jul 9 15:33:38 2020 - Merge pull request #25222 from tkashem/etcd-healthcheck-4.4
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. https://access.redhat.com/errata/RHBA-2020:2913