Bug 803651

Summary: Not clear description for using rhc-ctl-domain to updating not existing key
Product: OKD Reporter: bzhao
Component: ocAssignee: John (J5) Palmieri <johnp>
Status: CLOSED CURRENTRELEASE QA Contact: libra bugs <libra-bugs>
Severity: low Docs Contact:
Priority: high    
Version: 2.xCC: jkeck, mhicks, rmillner
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-04-13 18:34:28 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description bzhao 2012-03-15 11:09:44 UTC 
Description of problem:
It will prompt "Unable to read user public keyfile XX.pub" while you executed rhc-ctl-domain to updating an not existed key


Version-Release number of selected component (if applicable):
rhc-0.88.4-1.el6_2.noarch

How reproducible:
Always

Steps to Reproduce:
1.Call CLI to update a ssh key with no existing specific key-name
# rhc-ctl-domain --update-ssh-key XXX -k XXX.pub -p XXX

  
Actual results:
It will return "Unable to read user public keyfile XXX.pub"

Expected results:
It should prompt "Key name 'XXX' doesn't exist for user XXX"

Additional info:
Comment 1 John (J5) Palmieri 2012-04-09 18:33:44 UTC 
The error is triggered because the key file XXX.pub can not be read.  It doesn't even get to the point of querying the server for an existing key.  Does this happen if you give it a valid key file but non extant key name?  Otherwise the error is correct.
Comment 2 bzhao 2012-04-10 06:35:49 UTC 
Passed verification againt devenv_1704