Bug 1022932

Summary: engine-setup should not fail if /etc/ovirt-engine/.pgpass exists
Product: Red Hat Enterprise Virtualization Manager Reporter: Yedidyah Bar David <didi>
Component: ovirt-engine-setupAssignee: Yedidyah Bar David <didi>
Status: CLOSED CURRENTRELEASE QA Contact: sefi litmanovich <slitmano>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.3.0CC: acathrow, bazulay, iheim, oschreib, Rhev-m-bugs, sbonazzo, scohen, yeylon
Target Milestone: ---Keywords: Triaged
Target Release: 3.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: integration
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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:

Description Yedidyah Bar David 2013-10-24 09:41:55 UTC
Description of problem:

/etc/ovirt-engine/.pgpass was used by releases up to and including 3.2 to store database access credentials. 3.3 checks this file during upgrade from 3.2, but also on a new setup, if it exists, and fails if the credentials there point to an inaccessible database.

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


How reproducible:
Always

Steps to Reproduce:
1. Install 3.2
2. run engine-setup
3. Copy /etc/ovirt-engine/.pgpass to a backup elsewhere
4. engine-cleanup
5. Install (or upgrade to) 3.3
6. Copy the backup back to /etc/ovirt-engine/.pgpass
7. run engine-setup

Actual results:

engine-setup fails with:

[ ERROR ] Failed to execute stage 'Misc configuration': FATAL:  Ident authentication failed for user "engine" FATAL:  Ident authentication failed for user "engine"

Expected results:

engine-setup should continue, ignoring this file and creating a new database or connect to an existing one as chosen by the user

Additional info:

This file is cleaned by 3.2's engine-cleanup.

3.3.'s engine-setup used to leave it behind as-is until recently. Now it zeros it.

3.3.'s engine-cleaup does not touch it.

Comment 1 sefi litmanovich 2013-12-16 14:02:12 UTC
Verified on rhevm3.3 is27, works for >= is24.

reproduced as per description with update from rhevm 3.2 sf22 to rhevm 3.3 is27.

Comment 2 Itamar Heim 2014-01-21 22:21:40 UTC
Closing - RHEV 3.3 Released

Comment 3 Itamar Heim 2014-01-21 22:26:58 UTC
Closing - RHEV 3.3 Released