Bug 1908337 - [v2v] VM import RHV to Vmware remove memory limits from VM Spec
Summary: [v2v] VM import RHV to Vmware remove memory limits from VM Spec
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: V2V
Version: 2.5.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 2.5.3
Assignee: Sam Lucidi
QA Contact: Amos Mastbaum
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-12-16 13:01 UTC by Amos Mastbaum
Modified: 2021-03-15 19:29 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-03-15 19:29:39 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Amos Mastbaum 2020-12-16 13:01:51 UTC 
Description of problem:

Please refer to Roman's comment:
https://bugzilla.redhat.com/show_bug.cgi?id=1904051#12

"...
Until we support something like ballooning, setting a limit at all only make sense when the VM should run in the QoS class "Guaranteed". There it will have to be exactly the same like the "request". At this stage setting a limit different than the request makes for almost 100% of all users no sense in CNV.

So first, the import step should not set a limit. .."


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Sam Lucidi 2020-12-16 20:15:11 UTC 
https://github.com/kubevirt/vm-import-operator/pull/454
Comment 2 Ilanit Stein 2020-12-20 12:00:12 UTC 
@Fabien, we already have a CNV-2.5.3 build. Should this bug move to ON_QA?
Comment 3 Ilanit Stein 2020-12-30 09:38:22 UTC 
Verified on OCP-4.6/CNV hco-v2.5.3-64

Memory limit field do not exist on an imported VM from RHV like before:
 
From imported VM yaml:
        memory: {}
        resources:
          requests:
            memory: 1Gi
      evictionStrategy: LiveMigrate
Note You need to log in before you can comment on or make changes to this bug.