Bug 2244869 - MTQ does not work with Auto Memory Limits
Summary: MTQ does not work with Auto Memory Limits
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.1
Assignee: Barak
QA Contact: Kedar Bidarkar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-10-18 16:31 UTC by Denys Shchedrivyi
Modified: 2024-01-09 10:31 UTC (History)
2 users (show)

Fixed In Version: v4.14.1.rhel9-8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-12-07 15:02:12 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github kubevirt managed-tenant-quota pull 35 0 None Merged [release-v1.1] Bump kubevirt to v1.0.1 for AutoResourceLimitsGate FG 2023-11-15 11:21:50 UTC
Red Hat Issue Tracker CNV-34138 0 None None None 2023-10-18 16:32:22 UTC
Red Hat Product Errata RHSA-2023:7704 0 None None None 2023-12-07 15:02:14 UTC

Description Denys Shchedrivyi 2023-10-18 16:31:44 UTC
Description of problem:
 Managed-Tenant-Quota does not help with increasing quotas for VM that set the memory lmits automatically (using Kubevirt featureGate: `AutoResourceLimitsGate`)

 The POD has memory requests and limits:

> $ oc get pod virt-launcher-vm-fedora-guest-memory-96ck7 -o json | jq .spec.containers[0].resources
> {
>   "limits": {
>     "memory": "2536Mi"
>   },
>   "requests": {
>     "memory": "1268Mi"
>   }
> }

 And VMMRQ is big enough:

> $ oc get vmmrq my-vmmrq-big -o json |  jq .spec
> {
>   "additionalMigrationResources": {
>     "limits.memory": "5Gi",
>     "requests.memory": "5Gi"
>   }
> }

But migration is still in Pending state:

> $ oc get vmim
> NAME                        PHASE     VMI
> kubevirt-migrate-vm-dcrvp   Pending   vm-fedora-guest-memory



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

How reproducible:
100%

Steps to Reproduce:
1. enable FG in kubevirt: AutoResourceLimitsGate
2. create VM with memory guest (without limits)
3. create resourcequota
4. create vmmrq
5. migrate VM

Actual results:
 Migration is in Pending state


Expected results:
 Migration completed


Additional info:

 Perhaps, this issue related to bug 2241953

Comment 1 Denys Shchedrivyi 2023-11-27 19:17:26 UTC
Verified on CNV-v4.14.1.rhel9-62, MTQ with Auto Memory Limits (AutoResourceLimitsGate) works well

Comment 8 errata-xmlrpc 2023-12-07 15:02:12 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.1 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:7704


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