+++ This bug was initially created as a clone of Bug #1843462 +++ +++ This bug was initially created as a clone of Bug #1843187 +++ When pod expectations are not met, status for workloads can wedge. When status for workloads wedges, operators wait indefinitely. When operators wait indefinitely status is wrong. When status is wrong, upgrades can fail. Picking https://github.com/kubernetes/kubernetes/pull/91008 seems like a fix. --- Additional comment from Maciej Szulik on 2020-06-03 12:54:58 CEST ---
This waiting to be merged in the queue.
Confirmed with payload: 4.4.0-0.nightly-2020-06-27-171816, user login OCP ， and open two terminals , on the first terminal delete one pod, on the second terminal scale down the deployment , no new pod created and no other pods deleted: [zhouying@dhcp-140-138 ~]$ oc get po NAME READY STATUS RESTARTS AGE my-dep-58668cd74d-chcmh 1/1 Running 0 101s my-dep-58668cd74d-vj2dr 1/1 Running 0 54s my-dep-58668cd74d-w4ww5 1/1 Running 0 54s [zhouying@dhcp-140-138 ~]$ oc scale deploy/my-dep --replicas=2 deployment.apps/my-dep scaled [zhouying@dhcp-140-138 ~]$ oc get po NAME READY STATUS RESTARTS AGE my-dep-58668cd74d-chcmh 1/1 Running 0 3m22s my-dep-58668cd74d-vj2dr 1/1 Running 0 2m35s
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:2786