Description of problem: New rhc server command doesn't respond well if run against an older server. Version-Release number of selected component (if applicable): rhc-1.1.11 Steps to Reproduce: 1. Set up an OpenShift Enterprise installation 2. run rhc server against it Actual results: [demo1126@lmeyer-client ~]$ LIBRA_SERVER=broker rhc server /usr/lib/ruby/gems/1.8/gems/rest-client-1.6.1/lib/restclient/abstract_response.rb:48:in `return!': 404 Resource Not Found (RestClient::ResourceNotFound) from /usr/lib/ruby/gems/1.8/gems/rest-client-1.6.1/lib/restclient/request.rb:220:in `process_result' from /usr/lib/ruby/gems/1.8/gems/rest-client-1.6.1/lib/restclient/request.rb:169:in `transmit' [...] Expected results: A coherent error message about this server not supporting this functionality. Additional info: It appears to be hitting /app/status/status.json which... I'm not even sure what is supposed to supply that, but nothing does in OSE so it's a 404.
The status site, which is openshift online only. Fixed in my debt branch - it will display the api version on other servers. smarterclayton/help_refactor_and_apps_command
US3117
Was fixed and delivered.
It's displayed api version with fork_ami_us3117_refactor_help_and_cleanup_with_bug_fixes_327 as below: # rhc server Connected to localhost Login to localhost: Password: Using API version 1.3