Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1134444

Summary: engine-setup completes correctly only if the engine DB names matches the engine username
Product: Red Hat Enterprise Virtualization Manager Reporter: Simone Tiraboschi <stirabos>
Component: ovirt-engine-setupAssignee: Simone Tiraboschi <stirabos>
Status: CLOSED CURRENTRELEASE QA Contact: movciari
Severity: medium Docs Contact:
Priority: urgent    
Version: 3.4.0CC: bazulay, ecohen, gklein, iheim, rbalakri, Rhev-m-bugs, sbonazzo, scohen, yeylon
Target Milestone: ---   
Target Release: 3.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: integration
Fixed In Version: org.ovirt.engine-root-3.5.0-11 Doc Type: Bug Fix
Doc Text:
previously rhevm-setup completed correctly only if the engine DB names matched the engine username cause it inverted the database name and the username writing pg_hba.conf file. Now the pg_hba.conf is written correctly.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-12 14:09:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1156114    
Bug Blocks: 1142923, 1156165    
Attachments:
Description Flags
first answerfile
none
cleanup answerfile
none
third answerfile
none
failing answerfile none

Description Simone Tiraboschi 2014-08-27 14:04:08 UTC 
Description of problem:
rhevm-setup completes correctly only if the engine DB names matches the engine username cause it inverts the database name and the username writing pg_hba.conf file.

Version-Release number of selected component (if applicable):
av11.1

How reproducible:
100%, automatically and manually

Steps to Reproduce:
1. rhevm-setup --config-append=working 
2. rhevm-cleanup --config-append=cleanup 
3. rhevm-setup --config-append=setup 

Actual results:
'Misc configuration': Command '/usr/share/ovirt-engine/dbscripts/create_schema.sh' failed to execute

Expected results:
rhevm-setup completes correctly

Additional info:
To reproduce please modify OVESETUP_CONFIG/fqdn and OVESETUP_PKI/organization in the attached files matching your hostname.
Comment 1 Simone Tiraboschi 2014-08-27 14:12:29 UTC 
Created attachment 931493 [details]
first answerfile
Comment 2 Simone Tiraboschi 2014-08-27 14:13:34 UTC 
Created attachment 931494 [details]
cleanup answerfile
Comment 3 Simone Tiraboschi 2014-08-27 14:14:03 UTC 
Created attachment 931495 [details]
third answerfile
Comment 4 Petr Beňas 2014-09-02 12:19:55 UTC 
Notes for QE: use different DB name in the answerfile.
Comment 5 movciari 2014-10-22 11:21:55 UTC 
failed on vt6 with engine DB name in answerfile set to engineDB, saying database engineDB does not exist (automatic DB provisioning was enabled)
Comment 6 movciari 2014-10-22 11:22:36 UTC 
Created attachment 949348 [details]
failing answerfile
Comment 7 Simone Tiraboschi 2014-10-23 15:06:23 UTC 
Unfortunately movciari found a new bug: it seams that we are not able to correctly handle DB names with mixed case as 'engineDB'.

Using 'enginedb' for the DB name and 'engine' for the username works as expected while instead using 'enginE' for the DB and 'enginE' for the username doesn't.
Comment 8 movciari 2014-10-29 13:32:12 UTC 
i will wait for 1156114 to be ON_QA to verify it at once