Bug 1549931

Summary: Trigger a deploy of DC manually caused too much time to finish because of evicted pods.
Product: OpenShift Container Platform Reporter: Wang Haoran <haowang>
Component: MasterAssignee: Tomáš Nožička <tnozicka>
Status: CLOSED ERRATA QA Contact: Wang Haoran <haowang>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.9.0CC: aos-bugs, jokerman, mfojtik, mmccomas, tnozicka, xtian
Target Milestone: ---   
Target Release: 3.10.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: Some of the DC pods get evicted. Consequence: DC with recreate strategy waits for them until timeout is reached. Fix: DC no longer waits for evicted Pods as there is no reason to. Result: DC recreate strategy works fine even if evicted pods are present.
Story Points: ---
Clone Of:
: 1590059 (view as bug list) Environment:
Last Closed: 2018-07-30 19:10:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 1590059    

Description Wang Haoran 2018-02-28 05:25:23 UTC
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:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

Comment 1 Wang Haoran 2018-02-28 05:26:46 UTC
Per comment here:https://bugzilla.redhat.com/show_bug.cgi?id=1547169#c11

Comment 2 Tomáš Nožička 2018-03-20 13:22:21 UTC
master PR https://github.com/openshift/origin/pull/19029

3.9 will follow when that merges

Comment 3 Wang Haoran 2018-05-14 06:56:17 UTC
Verified with:
openshift v3.10.0-0.41.0
kubernetes v1.10.0+b81c8f8
etcd 3.2.16

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.

Comment 5 Tomáš Nožička 2018-06-11 12:04:53 UTC

Comment 8 errata-xmlrpc 2018-07-30 19:10:04 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, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.