Bug 1814547
Summary: | [Descheduler] Duplicate strategy is evicting the deploy pod in the RC which is preventing new pods from being created | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | RamaKasturi <knarra> |
Component: | kube-scheduler | Assignee: | Mike Dame <mdame> |
Status: | CLOSED ERRATA | QA Contact: | RamaKasturi <knarra> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.5 | CC: | aos-bugs, mfojtik |
Target Milestone: | --- | ||
Target Release: | 4.5.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause: Descheduler RemoveDuplicates strategy considered any pods with the same ownerref to be duplicates and would indiscriminately evict some of them at random
Consequence: DeploymentConfigs create a separate "deploy" pod, which is not one of the replicas but does have the same ownerref as a replica. When the descheduler evicted this pod, it did not get recreated and this broke the DC.
Fix: Add stricter requirements for what is considered a duplicate pod (including verifying the same images used) and add an optional field to exclude certain kinds of ownerrefs , such as DeploymentConfigs.
Result: This issue is no longer present with DCs
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2020-07-13 17:22:24 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: |
Description
RamaKasturi
2020-03-18 07:56:28 UTC
We spoke about it with Mike and I doubt we'll fix it for 4.4, moving to 4.5 Pr upstream to address this in a quick way: https://github.com/kubernetes-sigs/descheduler/pull/275 Verified with the payload below and do not see the issue happening, moving the bug to verified state. [ramakasturinarra@dhcp35-60 Downloads]$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.5.0-0.nightly-2020-05-21-072118 True False 3h9m Cluster version is 4.5.0-0.nightly-2020-05-21-072118 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:2409 |