Bug 786392 - Faile to access postgreSQL after move app from one node to another one.
Summary: Faile to access postgreSQL after move app from one node to another one.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OKD
Classification: Red Hat
Component: Containers
Version: 1.x
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Dan McPherson
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-01 10:25 UTC by Johnny Liu
Modified: 2012-02-02 23:56 UTC (History)
0 users

Fixed In Version: rhc-cartridge-postgresql-8.4-0.2.5
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-02 23:56:04 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Johnny Liu 2012-02-01 10:25:39 UTC
Description of problem:
Faile to access postgreSQL after move app from one node to another one.

Version-Release number of selected component (if applicable):
rubygem-cloud-sdk-node-0.3.16-1.el6_2.noarch
rubygem-cloud-sdk-common-0.3.14-1.el6_2.noarch
rubygem-cloud-sdk-controller-0.3.21-1.el6_2.noarch
rhc-broker-0.85.27-1.el6_2.noarch


How reproducible:
Always

Steps to Reproduce:
1. Setup a multi-node env.
2. Create jbossas app and embed postgreSQL to it
3. Write a test page to access postgreSQL successfully.
4. Run "rhc-admin-move" command to move this app form one node to another in instance.
5. Access postgreSQL again.
  
Actual results:
Faile to access postgreSQL. Check postgreSQL process via "ps" or "netstat", found nothing.

Expected results:
postgreSQL should be always available after move this app.

Additional info:

Comment 1 Johnny Liu 2012-02-02 06:56:37 UTC
Verified this bug on devenv_stage_117, and PASSED.

Comment 2 Johnny Liu 2012-02-02 09:10:27 UTC
(In reply to comment #1)
> Verified this bug on devenv_stage_117, and PASSED.

Ooops, should be:
Verified this bug on devenv_stage_119, and PASSED.

Comment 3 Mrunal Patel 2012-02-02 23:56:04 UTC
Closing verified bugs.


Note You need to log in before you can comment on or make changes to this bug.