Description of problem: The "exit_code" field in message property is null, even if invoking a REST API successfully. Instead of nulls, the exit codes in REST API should be meaningful. Version-Release number of selected component (if applicable): devenv_3360 REST API 1.5 How reproducible: always Steps to Reproduce: 1. create a scaling python-3.3 application rhc app create py33 python-3.3 -s 2. My test covers the following APIs, and all the exit_codes are null: curl -k --user zhewang+1:redhat https://ec2-204-236-240-35.compute-1.amazonaws.com/broker/rest/domains/dev3360tst | python -m json.tool curl -k --user zhewang+1:redhat https://ec2-204-236-240-35.compute-1.amazonaws.com/broker/rest/domains/dev3360tst/applications/ | python -m json.tool curl -k --user zhewang+1:redhat https://ec2-204-236-240-35.compute-1.amazonaws.com/broker/rest/domains/dev3360tst/applications/py33 | python -m json.tool curl -k --user zhewang+1:redhat https://ec2-204-236-240-35.compute-1.amazonaws.com/broker/rest/domains/dev3360tst/applications/py33/events -d event=restart -XPOST | python -m json.tool Actual results: All the exit codes after successfully invoking the APIs in Step 2 are null. For instance, "messages": [ { "exit_code": null, "field": null, "severity": "info", "text": "Application 'py33' found" } ], Expected results: The exit codes in REST API should be meaningful values. Additional info:
https://github.com/openshift/origin-server/pull/2851
Commit pushed to master at https://github.com/openshift/origin-server https://github.com/openshift/origin-server/commit/b645042153a8fc8707bcaf3c1d09a417e676c5d1 Bug 974493
Verified in devenv_3373. For example, after invoking the domain API, the returned messages are: "messages": [ { "exit_code": 0, "field": null, "severity": "info", "text": "Found domain dev3373tst" } ],