Bug 1478959 - Increase of HE VM memory, raises tracebacks under VDSM log
Increase of HE VM memory, raises tracebacks under VDSM log
Status: NEW
Product: ovirt-engine
Classification: oVirt
Component: BLL.HostedEngine (Show other bugs)
x86_64 Linux
low Severity low (vote)
: ovirt-4.3.0
: ---
Assigned To: Denis Chaplygin
meital avital
: ZStream
Depends On:
Blocks: 1523835
  Show dependency treegraph
Reported: 2017-08-07 11:05 EDT by Artyom
Modified: 2017-12-08 15:30 EST (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1523835 (view as bug list)
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: SLA
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
dfediuck: ovirt‑4.3+

Attachments (Terms of Use)
vdsm log (14.57 MB, text/plain)
2017-08-07 11:05 EDT, Artyom
no flags Details

  None (edit)
Description Artyom 2017-08-07 11:05:53 EDT
Created attachment 1310157 [details]
vdsm log

Description of problem:
Increase of HE VM memory raises tracebacks under VDSM log

2017-08-07 17:55:15,246+0300 ERROR (jsonrpc/5) [virt.vm] (vmId='b58fdeda-45bb-43d2-b336-ef9953171347') hotplugMemory failed (vm:2971)
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2969, in hotplugMemory
  File "/usr/lib/python2.7/site-packages/vdsm/virt/virdomain.py", line 95, in f
    ret = attr(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/vdsm/libvirtconnection.py", line 125, in wrapper
    ret = f(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 586, in wrapper
    return func(inst, *args, **kwargs)
  File "/usr/lib64/python2.7/site-packages/libvirt.py", line 540, in attachDevice
    if ret == -1: raise libvirtError ('virDomainAttachDevice() failed', dom=self)
libvirtError: unsupported configuration: Attaching memory device with size '1966080' would exceed domain's maxMemory config

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

How reproducible:

Steps to Reproduce:
1. Deploy hosted-engine
2. Add master storage domain
3. Wait for auto-import operation
4. Increase amount of HE VM memory via UI

Actual results:
Action succeeds under the engine, but I can see Traceback under vdsm log

Expected results:
Action succeeds under the engine and vdsm log does not have any new tracebacks

Additional info:
Comment 1 Michal Skrivanek 2017-08-08 03:03:23 EDT
what's the maximum memory value in engine's HE VM dialog?
Comment 2 Artyom 2017-08-08 07:21:09 EDT
16Gb, I installed HE VM with 4Gb of memory, so max value is 4 * memory.
Comment 3 Artyom 2017-08-08 07:22:15 EDT
I believe the problem that the vdsm receive command for memory hotplug, when we still do not support it under the HE VM.
Comment 4 Michal Skrivanek 2017-08-08 07:27:37 EDT
(In reply to Artyom from comment #2)
> 16Gb, I installed HE VM with 4Gb of memory, so max value is 4 * memory.

nope it's started with 4GB as well, hence you're unable to hot plug anything more. Indeed it may not be supported
Comment 5 Martin Sivák 2017-08-14 10:24:48 EDT
Memory hotplug for hosted engine is still not supported and there used to be a condition in the engine code that skipped the call for hosted engine. I know Michal was not fond of it, but it should have prevented this error.

Btw: Did the apply now / later dialog show up?
Comment 6 Artyom 2017-08-15 07:12:25 EDT
No, when I update the memory, it does not show "Apply Later" dialog.
Comment 7 Yaniv Kaul 2017-11-22 03:29:22 EST
If memory hotplug for HE VM is not supported, why is the bug targeted for 4.2.0?
Comment 8 Doron Fediuck 2017-11-23 08:13:57 EST
Moving forward since we're done with 4.2.

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