Bug 2221801 - Unable to set autoCPULimitNamespaceLabelSelector via HCO CR
Summary: Unable to set autoCPULimitNamespaceLabelSelector via HCO CR
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Virtualization
Version: 4.14.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.14.0
Assignee: Jed Lejosne
QA Contact: zhe peng
URL:
Whiteboard:
: 2214362 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-10 20:02 UTC by Denys Shchedrivyi
Modified: 2023-11-08 14:06 UTC (History)
1 user (show)

Fixed In Version: v4.14.0.rhel9-1569
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-11-08 14:05:53 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github kubevirt hyperconverged-cluster-operator pull 2463 0 None Merged Add support for automatic CPU limits 2023-08-16 10:55:06 UTC
Red Hat Issue Tracker CNV-30842 0 None None None 2023-07-10 20:05:04 UTC
Red Hat Product Errata RHSA-2023:6817 0 None None None 2023-11-08 14:06:02 UTC

Description Denys Shchedrivyi 2023-07-10 20:02:06 UTC 
Description of problem:

Unable to set autoCPULimitNamespaceLabelSelector via HCO CR

The only option to set it now - use the json patch annotations which is a work around, so it would be better to be able to manage  autoCPULimitNamespaceLabelSelector directly in HCO CR configuration

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
 

Expected results:


Additional info:
Comment 1 zhe peng 2023-08-21 05:52:25 UTC 
verify with build: CNV-v4.14.0.rhel9-1632

step:
1. Edit HCO, add 
....
 resourceRequirements:
    autoCPULimitNamespaceLabelSelector:
      matchLabels:
        autocpulimit: "true"
....

saved.

2. create a namespace with label
  autocpulimit: "true"

3. create a vm in new namespace

vm running w/o error.

4. change  vmiCPUAllocationRatio to 1 and saved.
Get error: Invalid value: "object": Automatic CPU limits are incompatible with a VMI CPU allocation ratio of 1

move to verified.
Comment 2 Jed Lejosne 2023-08-21 13:17:27 UTC 
*** Bug 2214362 has been marked as a duplicate of this bug. ***
Comment 4 errata-xmlrpc 2023-11-08 14:05:53 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 (Important: OpenShift Virtualization 4.14.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-2023:6817
Note You need to log in before you can comment on or make changes to this bug.