Bug 1953484

Summary:	New OCP priority classes are not used - Storage
Product:	Container Native Virtualization (CNV)	Reporter:	Fabian Deutsch <fdeutsch>
Component:	Storage	Assignee:	Alexander Wels <awels>
Status:	CLOSED ERRATA	QA Contact:	dalia <dafrank>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	2.6.0	CC:	alitke, cnv-qe-bugs, yadu
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-11-02 15:57:28 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:36:43 UTC

Description of problem:
OCP has changed the names of priority classes. This component's _infrastructure pods_ priority 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 3 dalia 2021-09-09 08:31:08 UTC

verified on CNV-4.9, CDI v1.38.0-5

Comment 6 errata-xmlrpc 2021-11-02 15:57:28 UTC

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 (Moderate: OpenShift Virtualization 4.9.0 Images security and bug fix update), 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/RHSA-2021:4104