Description of problem: Run "rhc app reload" and it always return "Node execution failure" Version-Release number of selected component (if applicable): fork_ami_US2105_129 How reproducible: Always Steps to Reproduce: 1.Create an app 2.Reload it $ rhc app reload -a <app_name> 3. Actual results: Problem reported from server. Response code was 500. DEBUG: runcon: /var/lib/stickshift/2320bf8c730e492dab73fd8821076092/jbossas-7/app1_ctl.sh: No such file or directory Cartridge return code: 127 Exit Code: 143 broker_c: namespacerhloginsshapp_uuiddebugaltercartridgecart_typeactionapp_nameapi api_c: placeholder API version: 1.1.3 RESULT: Node execution failure (invalid exit code from node). If the problem persists please contact Red Hat support. Expected results: The app should be reloaded successfully. Additional info:
Fixed with commit 96eddebee3a578d68ee4434be7333fa99c98da3c. Will be available in next AMI for US 2105.
Verified it on fork_ami_2105_133, it's fixed now [root@F17x64-openshift test]# rhc app reload -a appname31417 -l xtian+t0 -p 1 RESULT: Success [root@F17x64-openshift test]# rhc app status -a appname31417 -l xtian+t0 -p 1 RESULT: Total Accesses: 1 Total kBytes: 0 Uptime: 2024 ReqPerSec: .000494071 BytesPerSec: 0 BytesPerReq: 0 BusyWorkers: 1 IdleWorkers: 0 Scoreboard: WS...