Bug 1108459

Summary: [origin_ui_180]Could add/configure server to an invaild nickname but can't use it
Product: OpenShift Online Reporter: XiuJuan Wang <xiuwang>
Component: ocAssignee: Fabiano Franz <ffranz>
Status: CLOSED WONTFIX QA Contact: libra bugs <libra-bugs>
Severity: low Docs Contact:
Priority: medium    
Version: 2.xCC: jliggitt, jokerman, mmccomas
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1130094 (view as bug list) Environment:
Last Closed: 2017-05-31 18:22:11 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1130094    

Description XiuJuan Wang 2014-06-12 05:48:37 UTC
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:

Comment 1 XiuJuan Wang 2014-06-16 09:45:04 UTC
Could reproduce this bug in rhc build from fork_ami_origin_ui_180_1209

Comment 2 Eric Paris 2017-05-31 18:22:11 UTC
We apologize, however, we do not plan to address this report at this time. The majority of our active development is for the v3 version of OpenShift. If you would like for Red Hat to reconsider this decision, please reach out to your support representative. We are very sorry for any inconvenience this may cause.