Bug 880107

Summary: Can't move zend app successfully across district or without district or from no district node to district node
Product: OKD Reporter: Rony Gong 🔥 <qgong>
Component: PodAssignee: Lili Nader <lnader>
Status: CLOSED DUPLICATE QA Contact: libra bugs <libra-bugs>
Severity: low Docs Contact:
Priority: medium    
Version: 2.xCC: mfisher
Target Milestone: ---Keywords: Regression
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-11-26 20:41:20 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 Rony Gong 🔥 2012-11-26 09:35:52 UTC
Description of problem:
Can't move zend app success across district successfully, caused by start this app when move
Permission denied: make_sock: could not bind to address 127.1.245.129:16083\nno listening sockets available, shutting down\nUnable to open logs\nFailed to start zend-5.6\n", :data=>{:exitcode=>121, :output=>"Starting Deployment \e[32m[OK]\e[0m\n[26.11.2012 03:14:58 SYSTEM] watchdog for zdd is running. 

Version-Release number of selected component (if applicable):
devenv_2518

How reproducible:
always

Steps to Reproduce:
1.Create multi node env and create 2 districts then add nodes to them
2.Create zend app
3.Move this zend app accross district
  
Actual results:
[root@ip-10-112-221-246 ~]# oo-admin-move --gear_uuid 7146a72df90d4af8b69deb894a8ad572 -i ip-10-152-131-32 --allow_change_district
URL: http://qzend2-qgong12.dev.rhcloud.com
Login: qgong
App UUID: 7146a72df90d4af8b69deb894a8ad572
Gear UUID: 7146a72df90d4af8b69deb894a8ad572
DEBUG: Source district uuid: 6848ca01690e427cb0c8cca5ca122418
DEBUG: Destination district uuid: 9d457eeccaf445a4a3fae8d59d0579ea
DEBUG: Getting existing app 'qzend2' status before moving
DEBUG: Gear component 'zend-5.6' was running
DEBUG: Stopping existing app cartridge 'zend-5.6' before moving
DEBUG: Force stopping existing app cartridge 'zend-5.6' before moving
DEBUG: Reserved uid '1005' on district: '9d457eeccaf445a4a3fae8d59d0579ea'
DEBUG: Creating new account for gear 'qzend2' on ip-10-152-131-32
DEBUG: Moving content for app 'qzend2', gear 'qzend2' to ip-10-152-131-32
Identity added: /var/www/openshift/broker/config/keys/rsync_id_rsa (/var/www/openshift/broker/config/keys/rsync_id_rsa)
Agent pid 18000
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 18000 killed;
DEBUG: Performing cartridge level move for 'zend-5.6' on ip-10-152-131-32
DEBUG: Starting cartridge 'zend-5.6' in 'qzend2' after move on ip-10-152-131-32
DEBUG: Moving failed.  Rolling back gear 'qzend2' 'qzend2' with remove-httpd-proxy on 'ip-10-152-131-32'
DEBUG: Moving failed.  Rolling back gear 'qzend2' in 'qzend2' with destroy on 'ip-10-152-131-32'
/opt/rh/ruby193/root/usr/share/gems/gems/openshift-origin-msg-broker-mcollective-1.2.1/lib/openshift/mcollective_application_container_proxy.rb:1190:in `run_cartridge_command': Node execution failure (invalid exit code from node).  If the problem persists please contact Red Hat support. (OpenShift::NodeException)
	from /var/www/openshift/broker/lib/express/broker/mcollective_ext.rb:12:in `run_cartridge_command'
	from /opt/rh/ruby193/root/usr/share/gems/gems/openshift-origin-msg-broker-mcollective-1.2.1/lib/openshift/mcollective_application_container_proxy.rb:585:in `block in move_gear_post'
	from /opt/rh/ruby193/root/usr/share/gems/gems/openshift-origin-msg-broker-mcollective-1.2.1/lib/openshift/mcollective_application_container_proxy.rb:577:in `each'
	from /opt/rh/ruby193/root/usr/share/gems/gems/openshift-origin-msg-broker-mcollective-1.2.1/lib/openshift/mcollective_application_container_proxy.rb:577:in `move_gear_post'
	from /opt/rh/ruby193/root/usr/share/gems/gems/openshift-origin-msg-broker-mcollective-1.2.1/lib/openshift/mcollective_application_container_proxy.rb:737:in `move_gear'
	from /usr/sbin/oo-admin-move:110:in `<main>'


Expected results:
Could be moved successfully

Additional info:

Comment 1 Lili Nader 2012-11-26 20:41:20 UTC

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