Bug 1323748 - webadmin does not show correct HE VM parameters, if it started with custom configuration file
Summary: webadmin does not show correct HE VM parameters, if it started with custom co...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.HostedEngine
Version: 3.6.5
Hardware: x86_64
OS: Linux
unspecified
medium vote
Target Milestone: ---
: ---
Assignee: Roy Golan
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-04 15:18 UTC by Artyom
Modified: 2017-05-11 09:31 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-17 07:19:22 UTC
oVirt Team: SLA
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?


Attachments (Terms of Use)

Description Artyom 2016-04-04 15:18:37 UTC
Description of problem:
Webadmin does not show correct HE VM parameters, if it started with custom configuration file(see also https://bugzilla.redhat.com/show_bug.cgi?id=1309572)

Version-Release number of selected component (if applicable):
rhevm-3.6.5-0.1.el6.noarch

How reproducible:
Always

Steps to Reproduce:
1. set global maintenance mode: hosted-engine --set-maintenance --mode=global 
2. poweroff engine VM if somehow up: hosted-engine --vm-poweroff
3. copy /var/run/ovirt-hosted-engine-ha/vm.conf to /tmp/my-vm.conf somewhere as a template
4. edit memory parameter from 4Gb to 8Gb(memSize=8192)
5. restart engine VM with a custom vm.conf: hosted-engine --vm-start --vm-conf=/tmp/my-vm.conf


Actual results:
HE VM succeeds to start, but webadmin show that HE VM has only 4Gb

Expected results:
Webadmin must show correct HE VM parameters(in my case it must be equal to 8Gb)

Additional info:
if I enter to VM I see that VM has 8Gb of memory and also vdsClient show me that VM has 8Gb so looks like engine DB does not update according to new HE VM configuration.

Comment 1 Roy Golan 2016-04-10 10:11:19 UTC
You're scenario is a 'fallback' scenario and by design this will not reflect the changes in the DB. It's other way round, the db is represented in the OVF xml and that is converted to the vm.conf. If you changed that we can't do nothing with it.

Comment 2 Artyom 2016-04-10 10:27:13 UTC
So you can close it, as not a bug. I just thought that any changes on the HE VM must be reflected under the engine.


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