Bug 1836971
Summary: | [Descheduler] - Indicate in the cluster pod logs that --dry-run is enabled for descheduler | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | RamaKasturi <knarra> |
Component: | kube-scheduler | Assignee: | Jan Chaloupka <jchaloup> |
Status: | CLOSED ERRATA | QA Contact: | RamaKasturi <knarra> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.5 | CC: | aos-bugs, jchaloup, mfojtik |
Target Milestone: | --- | Keywords: | UpcomingSprint |
Target Release: | 4.5.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | No Doc Update | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-07-13 17:39:55 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-05-18 15:06:06 UTC
Verified bug with the payload below and i see that when ever dry run is enabled cluster logs indicate that "Evicted pod in dry run mode: <pod_name> in namespace <name>" [ramakasturinarra@dhcp35-60 ~]$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.5.0-0.nightly-2020-05-27-234738 True False 9h Cluster version is 4.5.0-0.nightly-2020-05-27-234738 However for some of the strategies when dry run is enabled two log messages are shown where in which first one indicates it is a dry run but second one shows the pod is evicted and this might be creating confusion for the user, raised another bug(https://bugzilla.redhat.com/show_bug.cgi?id=1841187) to get this fixed and moving this to verified since the motto of this bug was to make sure that when in dry-run cluster logs are printed saying pods are getting evicted in dry run which works. Based on the above results moving the bug to verified state. 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 |