+++ This bug was initially created as a clone of Bug #1122413 +++ Description of problem: Unnecessary message "Available regions are" show up while creating app with region when server has no regions # rhc app create app php-5.4 --region region --no-git Application Options ------------------- Domain: wjiang Cartridges: php-5.4 Gear Size: default Scaling: no Region: region Creating application 'app' ... Could not find region 'region'. Available regions are Version-Release number of selected component (if applicable): fork_ami_origin_ui_186_1229 rhc build from fork_ami_origin_ui_186_1229 How reproducible: always Steps to Reproduce: 1. Create app with region when server have no regions 2. 3. Actual results: # rhc app create app php-5.4 --region region --no-git Application Options ------------------- Domain: wjiang Cartridges: php-5.4 Gear Size: default Scaling: no Region: region Creating application 'app' ... Could not find region 'region'. Available regions are Expected results: The unnecessary message shouldn't show up. Additional info: --- Additional comment from Fabiano Franz on 2014-07-23 14:56:43 EDT --- Fixed in https://github.com/openshift/origin-server/pull/5644 --- Additional comment from openshift-github-bot on 2014-07-23 16:34:10 EDT --- Commit pushed to master at https://github.com/openshift/origin-server https://github.com/openshift/origin-server/commit/fc3f0ed5a6bc83cebe11f10f68e16a305c5e7cea Bug 1122413 - handle server without explicit regions --- Additional comment from weiwei jiang on 2014-07-24 01:29:36 EDT --- Checked with devenv_5003, and the issue can not reproduce, So verify this.
Upstream commit: commit fc3f0ed5a6bc83cebe11f10f68e16a305c5e7cea Author: fabianofranz <contact> Date: Wed Jul 23 12:39:52 2014 -0300 Bug 1122413 - handle server without explicit regions
Verified and pass on puddle-2-1-2014-08-01 Creating app with region when server has no regions,the message "Server does not support explicit regions." will show up.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-1095.html