Created attachment 611389 [details] development.log Description of problem: After move, I found the mongodb process isn't up, so conentc connect success. I found only ruby, perl, nodejs could work well, all other app embemd with mongodb can't work well after move. Version-Release number of selected component (if applicable): devenv_2140 How reproducible: always Steps to Reproduce: 1.Create multile node env, create 2 districts and add node to them. 2.Create non_scalable app like(python,jboss, php),embemd mongodb 3.Them move this app accross district rhc-admin-move --gear_uuid 7078fe275f7d4fea936c766b3bb21982 -i ip-10-122-75-125 --allow_change_district Actual results: ssh into this app [q2php-qgong.dev.rhcloud.com ~]\> mongo MongoDB shell version: 2.0.2 connecting to: 127.1.251.1:27017/admin Mon Sep 10 06:07:44 Error: couldn't connect to server 127.1.251.1:27017 shell/mongo.js:86 exception: connect failed Expected results: could connect mongodb success. Additional info: all other db like mysql and postgresql work well.
For scalabe app embed with mongodb, after move, check mongodb connection. [qsphp-qgong.dev.rhcloud.com ~]\> mongo MongoDB shell version: 2.0.2 connecting to: b13281fa37-qgong.dev.rhcloud.com:38036/admin Mon Sep 10 06:28:10 DBClientCursor::init call() failed Mon Sep 10 06:28:10 Error: Error during mongo startup. :: caused by :: DBClientBase::findN: transport error: b13281fa37-qgong.dev.rhcloud.com:38036 query: { whatsmyuri: 1 } shell/mongo.js:86 exception: connect failed
rajat looking at and expect to fix today
Order issue, if mongodb is called first on move, and framework later, it causes trouble. Fixed with rev#a8e3e5c2bd15f8ba1a6954e82726d915fecb4aaf in crankcase.repo! Pull request in queue.
(In reply to comment #3) > Order issue, if mongodb is called first on move, and framework later, it > causes trouble. Fixed with rev#a8e3e5c2bd15f8ba1a6954e82726d915fecb4aaf in > crankcase.repo! > Pull request in queue. https://github.com/openshift/crankcase/pull/472 is merged in devenv_2158 Above commit is in master, move it to ON_QA to verify.
verified