Red Hat Bugzilla – Bug 1018073
Cannot connect to the mysql/psql database for existing scalable apps after migration on STG
Last modified: 2015-05-14 19:29:53 EDT
Description of problem:
After stage upgrade to devenv-stage_493, existing scalable apps cannot connect to the mysql/psql db anymore.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Create scalable app with mysql and postgresql added
3.Try to connect to the mysql/psql from the scalable app
ERROR 1130 (HY000): Host 'ip-10-179-2-61.ec2.internal' is not allowed to connect to this MySQL server
psql: FATAL: no pg_hba.conf entry for host "10.179.2.61", user "adminfsrygr7", database "jbeap1s", SSL off
\> ping ex-std-node3.stg.rhcloud.com
PING ex-std-node3.stg.rhcloud.com (10.179.2.61) 56(84) bytes of data.
The dbs can be connected from the scalable app web gear.
It works fine on the INT after server upgrade.
The dbs can be connected from the rhcsh on the db-gear.
[52135d8ddbd93cdda6000657-bmeng1stg.stg.rhcloud.com 52135d8ddbd93cdda6000657]\> mysql
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 2
Server version: 5.1.69 Source distribution
Copyright (c) 2000, 2013, Oracle and/or its affiliates. All rights reserved.
Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
Tested on a single node upgrade to devenv-stage_493 from devenv-stage_486.
The mysql/psql db can be connected for scalable app.
I doubt this might be still caused by cartridge_version number has not been upgraded for sprint34 (similar to bug 1018134), which cause most changes for the cartridges have not been upgraded in STG since STG is running oo-admin-upgrade without --ignore-cartridge-version option.
Tested on current STG (devenv-stage_496), cannot reproduce this issue.
Bug fixed on STG, move bug to verified.