Roy Golan 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. Change-Id: I903d4c039be052ce0044f2a9eebe889cdfd5cb25 Signed-off-by: Roman Mohr <rmohr@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: Martin Sivák: Looks good to me, but someone else must approve Roman Mohr: Verified Jenkins CI: Passed CI tests Roy Golan: Looks good to me, approved -- To view, visit https://gerrit.ovirt.org/43373 To unsubscribe, visit https://gerrit.ovirt.org/settings Gerrit-MessageType: merged Gerrit-Change-Id: I903d4c039be052ce0044f2a9eebe889cdfd5cb25 Gerrit-PatchSet: 3 Gerrit-Project: ovirt-engine Gerrit-Branch: master Gerrit-Owner: Roman Mohr <rmohr@redhat.com> Gerrit-Reviewer: Jenkins CI Gerrit-Reviewer: Martin Sivák <msivak@redhat.com> Gerrit-Reviewer: Roman Mohr <rmohr@redhat.com> Gerrit-Reviewer: Roy Golan <rgolan@redhat.com> Gerrit-Reviewer: automation@ovirt.org