Bug 1871293 - [sig-arch] Managed cluster should ensure control plane pods do not run in best-effort QoS
Summary: [sig-arch] Managed cluster should ensure control plane pods do not run in bes...
Keywords:
Status: CLOSED DUPLICATE of bug 1871951
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Storage
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Fabio Bertinatto
QA Contact: Qin Ping
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-22 02:02 UTC by Maru Newby
Modified: 2020-09-03 12:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
[sig-arch] Managed cluster should ensure control plane pods do not run in best-effort QoS
Last Closed: 2020-09-03 12:11:55 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Maru Newby 2020-08-22 02:02:37 UTC
test:
[sig-arch] Managed cluster should ensure control plane pods do not run in best-effort QoS 

is failing frequently in CI, see search results:
https://search.ci.openshift.org/?maxAge=168h&context=1&type=bug%2Bjunit&name=&maxMatches=5&maxBytes=20971520&groupBy=job&search=%5C%5Bsig-arch%5C%5D+Managed+cluster+should+ensure+control+plane+pods+do+not+run+in+best-effort+QoS

The following job:

https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/release-openshift-origin-installer-e2e-gcp-4.5/1296952987435929600

Is representative of the failure mode seen across 40+ jobs in the search over the past 4 days:

fail [github.com/openshift/origin/test/extended/operators/qos.go:51]: Aug 22 00:27:49.273: 
1 pods found in best-effort QoS:
openshift-infra/recycler-for-nfs-scvrv is running in best-effort QoS

Comment 1 Fabio Bertinatto 2020-09-03 12:11:55 UTC
PR https://github.com/openshift/origin/pull/25315 fixed this on master. Backported to 4.5 in https://github.com/openshift/origin/pull/25316.

*** This bug has been marked as a duplicate of bug 1871951 ***


Note You need to log in before you can comment on or make changes to this bug.