Description of problem: Create a DeploymentConfig, after one pods evicted by the EvictionManager due to various node problem, will cause the next deploy cost too much time. Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Per comment here:https://bugzilla.redhat.com/show_bug.cgi?id=1547169#c11
master PR https://github.com/openshift/origin/pull/19029 3.9 will follow when that merges
Verified with: openshift v3.10.0-0.41.0 kubernetes v1.10.0+b81c8f8 etcd 3.2.16 steps: 1. Create an dc with Recreate Strategy 2. Create a large file on one of the node that running the workload, make the node underDiskPressure 3. trigger an deploy manually 4. check how long the new deploy will finished. resutls: the new deploy finished very quickly.
https://github.com/openshift/ose/pull/1307
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-2018:1816