This issue also exist in rhc-1.29.3.1-1.el6op.noarch.
Actually, this bug even could be reproduced with nickname beginning with number, such as "12", "1server", these names only contain alphanumeric characters.
[root@dhcp-129-188 workspace]# rhc server use 12
Invalid URI specified: 12
[root@dhcp-129-188 workspace]# rhc server show --server 1server
Invalid URI specified: 1server
+++ This bug was initially created as a clone of Bug #1108459 +++
Description of problem:
Could add/configure server to an invaild nickname but can't use it.
When use the nickname, will show "Invalid URI specified: <invaild-nickname>"
Version-Release number of selected component (if applicable):
rhc build from fork_ami_origin_ui_180_1204
How reproducible:
always
Steps to Reproduce:
1.Add a server and set to an invaild name , like "@#@"
2.Use this server with the nickname
3.
Actual results:
step1:
$ rhc server add stg.openshift.redhat.com "@#@" -l xiuwang --skip-wizard
Saving server configuration to /home/wxj/.openshift/servers.yml ... done
step 2:
$ rhc server use '@#@'
Invalid URI specified: @#@
[wxj@wangxiuj .openshift]$ rhc server configure "@#@" --nickname cad
Invalid URI specified: @#@
$ rhc server show --server "@#@"
Invalid URI specified: @#@
Expected results:
Should not add/configure server to invaild nickname.
Additional info:
--- Additional comment from XiuJuan Wang on 2014-06-16 05:45:04 EDT ---
Could reproduce this bug in rhc build from fork_ami_origin_ui_180_1209