Bug 1077267

Summary: Validate database max connections when applying schema
Product: [oVirt] ovirt-engine Reporter: Alon Bar-Lev <alonbl>
Component: Setup.EngineAssignee: Yedidyah Bar David <didi>
Status: CLOSED CURRENTRELEASE QA Contact: Karolína Hajná <khajna>
Severity: medium Docs Contact:
Priority: medium    
Version: ---CC: bugs, emesika, gklein, iheim, pstehlik, rbalakri, sbonazzo, yeylon
Target Milestone: ovirt-3.6.0-rcFlags: rule-engine: ovirt-3.6.0+
ylavi: planning_ack+
rule-engine: devel_ack+
pstehlik: testing_ack+
Target Release: 3.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-3.6.0-0.0.master.20150412172306.git55ba764 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-10 12:55:59 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:
Bug Depends On:    
Bug Blocks: 1072391    

Description Alon Bar-Lev 2014-03-17 15:30:16 UTC 
We have specific requirement for max conenctions, exists in DEFAULT_POSTGRES_PROVISIONING_MAX_CONN.

We should take it out of 'PROVISIONING' into common database environment.

Apply this when provisioning and verify the remote database settings when applying.

select setting from pg_settings where name='max_connections';
Comment 1 Alon Bar-Lev 2014-03-17 15:33:15 UTC 
Make sure to cast to int as the settings is text.
Comment 3 Karolína Hajná 2016-02-05 13:38:42 UTC 
Verified in rhevm-3.6.3-0.1.el6.noarch