Bug 1272542

Summary: [RFE] When restoring from backup using engine-backup and files is included in scope, perform sanity check on ENGINE_HEAP_MAX and ENGINE_HEAP_MIN
Product: Red Hat Enterprise Virtualization Manager Reporter: Allie DeVolder <adevolder>
Component: ovirt-engineAssignee: Yedidyah Bar David <didi>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: low    
Version: 3.5.4CC: awestbro, dfediuck, lsurette, rbalakri, Rhev-m-bugs, sbonazzo, srevivo, ykaul, ylavi
Target Milestone: ---Keywords: FutureFeature
Target Release: ---Flags: lsvaty: testing_plan_complete-
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-12 11:32:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Integration RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Allie DeVolder 2015-10-16 17:06:54 UTC
If you're restoring from backup on a system with more RAM than was available when the backup was created, then /etc/ovirt-engine/engine.conf.d/10-setup-java.conf could possibly contain conflicting values that would cause ovirt-engine to fail to run. 

In a production environment, when recovering from backup on a new system, ENGINE_HEAP_MAX="2g" was included in 10-setup-java.conf, while the initial engine-setup configuration set the ENGINE_HEAP_MIN to 4g, causing ovirt-engine to crash on startup for heap issues.

Comment 4 Yaniv Lavi 2018-06-12 11:32:09 UTC
Closing old RFEs, please reopen if still needed.
Patches are always welcome.

Comment 5 Franta Kust 2019-05-16 13:05:07 UTC
BZ<2>Jira Resync