Bug 889095

Summary: Database password not printed out when adding db cartridge to applications
Product: OpenShift Container Platform Reporter: Gaoyun Pei <gpei>
Component: ocAssignee: Brenton Leanhardt <bleanhar>
Status: CLOSED ERRATA QA Contact: libra bugs <libra-bugs>
Severity: high Docs Contact:
Priority: high    
Version: 1.2.0CC: bleanhar, ccoleman, jhou, libra-onpremise-devel, xjia, xtian
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 889090 Environment:
Last Closed: 2013-01-31 20:33:57 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: 889090    
Bug Blocks:    

Description Gaoyun Pei 2012-12-20 08:33:18 UTC 
Description of problem:
When adding db(mysql,postgresql) cartridge to an application in OSE, only connection url is displayed. The username, password and dbname are not printed out. 

Version-Release number of selected component (if applicable):
rhc-1.3.2
http://buildvm-devops.usersys.redhat.com/puddle/build/OpenShiftEnterprise/1.1.x/2012-12-19.2/

How reproducible:
Always

Steps to Reproduce:
1. Create an application
2. Add a db cartridge to the application
rhc cartridge add mysql-5.1 -a eap1
  
Actual results:
[hjw@rheltest devenv]$ rhc cartridge add mysql-5.1 -a eap1
Password: *
Adding 'mysql-5.1' to application 'eap1'
Success
mysql-5.1 (MySQL Database 5.1)
==============================
  Connection URL: mysql://127.1.3.1:3306/

[hjw@rheltest devenv]$ rhc cartridge show mysql-5.1 -a eap1 -px
mysql-5.1 (MySQL Database 5.1)
==============================
  Connection URL: mysql://127.1.3.1:3306/


Expected results:
Should print out username, password and dbname

+++ This bug was initially created as a clone of Bug #889090 +++

Description of problem:
When adding db(mysql, mongo, postgresql) cartridge to an application, only connection url is displayed. The username, password and dbname are not printed out. 

Version-Release number of selected component (if applicable):
rhc-1.3.2
On devenv_2613

How reproducible:
Always

Steps to Reproduce:
1. Create an application
2. Add a db cartridge to the application
rhc cartridge add mysql-5.1 -a eap1
  
Actual results:
[hjw@rheltest devenv]$ rhc cartridge add mysql-5.1 -a eap1
Password: *
Adding 'mysql-5.1' to application 'eap1'
Success
mysql-5.1 (MySQL Database 5.1)
==============================
  Connection URL: mysql://127.1.3.1:3306/

[hjw@rheltest devenv]$ rhc cartridge show mysql-5.1 -a eap1 -px
mysql-5.1 (MySQL Database 5.1)
==============================
  Connection URL: mysql://127.1.3.1:3306/


Expected results:
Should print out username, password and dbname

Additional info:
Comment 2 Clayton Coleman 2013-01-07 15:45:19 UTC 
I fixed this in the bug 889090, please verify
Comment 3 Brenton Leanhardt 2013-01-07 22:17:26 UTC 
This will ship with the  next puddle.
Comment 4 xjia 2013-01-08 03:08:26 UTC 
Verify:

[root@client ~]# rhc cartridge add mysql -pjia -a php
Adding 'mysql-5.1' to application 'php' ... Success
mysql-5.1 (MySQL Database 5.1)
==============================
  Connection URL: mysql://127.0.250.1:3306/
  Database Name:  php
  Password:       zpuetkRlVswC
  Username:       admin

RESULT:
Added mysql-5.1 to application php

MySQL 5.1 database added.  Please make note of these credentials:

   Root User: admin
   Root Password: zpuetkRlVswC
   Database Name: php

Connection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/

You can manage your new MySQL database by also embedding phpmyadmin-3.4.
The phpmyadmin username and password will be the same as the MySQL credentials above.

[root@client ~]# rhc -v
rhc 1.3.2

Version:
http://buildvm-devops.usersys.redhat.com/puddle/build/OpenShiftEnterprise/1.1.x/2013-01-07.2/
Comment 6 errata-xmlrpc 2013-01-31 20:33:57 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2013-0220.html