Change in ovirt-engine[ovirt-engine-3.6]: core: Update maxSchedulingMemory in VDS when related values ...

[piotr.kliczewski at gmail.com]

Piotr Kliczewski has submitted this change and it was merged.

Change subject: core: Update maxSchedulingMemory in VDS when related values change
......................................................................


core: Update maxSchedulingMemory in VDS when related values change

When cloning VDS instances the calculeated maxSchedulingMemory was calculated
wrong. Now VDS recalculates maxSchedulingMemory whenever a variable, which is
part of the calculation changes.

This bug had no consequences because maxSchedulingMemory is currently not read
from cloned VDS instances.

Bug-Url: https://bugzilla.redhat.com/show_bug.cgi?id=1180071
Change-Id: I903d4c039be052ce0044f2a9eebe889cdfd5cb25
Signed-off-by: Roman Mohr <rmohr at redhat.com>
---
M backend/manager/modules/common/src/main/java/org/ovirt/engine/core/common/businessentities/VDS.java
M backend/manager/modules/dal/src/main/java/org/ovirt/engine/core/dao/VdsDaoImpl.java
M backend/manager/modules/restapi/types/src/test/java/org/ovirt/engine/api/restapi/types/HostMapperTest.java
3 files changed, 4 insertions(+), 3 deletions(-)

Approvals:
  Piotr Kliczewski: Passed CI tests
  Martin Sivák: Verified
  Roy Golan: Looks good to me, approved



-- 
To view, visit https://gerrit.ovirt.org/50104
To unsubscribe, visit https://gerrit.ovirt.org/settings

Gerrit-MessageType: merged
Gerrit-Change-Id: I903d4c039be052ce0044f2a9eebe889cdfd5cb25
Gerrit-PatchSet: 2
Gerrit-Project: ovirt-engine
Gerrit-Branch: ovirt-engine-3.6
Gerrit-Owner: Martin Sivák <msivak at redhat.com>
Gerrit-Reviewer: Jenkins CI
Gerrit-Reviewer: Martin Sivák <msivak at redhat.com>
Gerrit-Reviewer: Piotr Kliczewski <piotr.kliczewski at gmail.com>
Gerrit-Reviewer: Roy Golan <rgolan at redhat.com>
Gerrit-Reviewer: Tal Nisan <tnisan at redhat.com>
Gerrit-Reviewer: gerrit-hooks <automation at ovirt.org>