Bug 1953479

Summary:	New OCP priority classes are not used - Virt
Product:	Container Native Virtualization (CNV)	Reporter:	Fabian Deutsch <fdeutsch>
Component:	Virtualization	Assignee:	aschuett <aschuett>
Status:	CLOSED NEXTRELEASE	QA Contact:	Israel Pinto <ipinto>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	2.6.0	CC:	cnv-qe-bugs, danken, kbidarka, sgott
Target Milestone:	---
Target Release:	4.9.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-06-30 12:23:09 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 Fabian Deutsch 2021-04-26 08:32:22 UTC

Description of problem:
OCP has changed hte names of priority classes. This component's _infrastructure pods_ classes should be added or adjusted accordingly to either system-cluster-critical or system-node-critical priority.

See https://mailman-int.corp.redhat.com/archives/aos-devel/2021-April/msg00402.html

The new classes must not be set on user workloads (i.e. VMs)

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:
Infrastructure components should carry the new priority classes


Additional info:

Comment 4 sgott 2021-06-30 12:23:09 UTC

We already use the highest priority values that are safe to use. If we raised them, we could compete with node level infrastructure that KubeVirt depends on to run.

Because we have not seen complaints that our current priority classes are an issue, we're opting not to change current values for now.