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: | Master | Assignee: | Tomáš Nožička <tnozicka> | |
| Status: | CLOSED ERRATA | QA Contact: | Wang Haoran <haowang> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | medium | |||
| Version: | 3.9.0 | CC: | aos-bugs, jokerman, mfojtik, mmccomas, tnozicka, xtian | |
| Target Milestone: | --- | |||
| Target Release: | 3.10.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| 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: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1590059 | |||
|
Description
Wang Haoran
2018-02-28 05:25:23 UTC
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. 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 |