Bug 865100

Summary: katello-configure -reset-db does not reset user password
Product: Red Hat Satellite Reporter: Miroslav Suchý <msuchy>
Component: InstallerAssignee: Katello Bug Bin <katello-bugs>
Status: CLOSED DUPLICATE QA Contact: Katello QA List <katello-qa-list>
Severity: low Docs Contact:
Priority: low    
Version: 6.0.0CC: bkearney, ehelms, mmccune
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-09-04 18:16:21 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:

Description Miroslav Suchý 2012-10-10 20:00:35 UTC 
Description of problem:
db user are not updated in second run of katello-configure

Version-Release number of selected component (if applicable):
katello-configure-1.1.10-1.git.93.01b51e4.el6.noarch

How reproducible:
alway

Steps to Reproduce:
1. run: katello-configure -b --db-name=katellodb --db-user=katello --db-password=olletak --deployment=katello
2. katello-configure -b --db-name=katellodb1 --db-user=katello1 --db-password=olletak1 --deployment=katello --reset-data=YES
3. select * from pg_user;
  
Actual results:
  usename  | usesysid | usecreatedb | usesuper | usecatupd |  passwd  | valuntil | useconfig 
-----------+----------+-------------+----------+-----------+----------+----------+-----------
 postgres  |       10 | t           | t        | t         | ******** |          | 
 katello   |    16384 | t           | f        | f         | ******** |          | 
...

Expected results:
I would expect user katello1 created, or if previously such user exist to modify its password or katello-configure to fail with error message.

Additional info:
Comment 2 Bryan Kearney 2014-09-04 18:16:21 UTC 
I realize that the older bug should be the duplicate, but the newer one is against  the new installer version. We will track this there.

*** This bug has been marked as a duplicate of bug 1125414 ***