Bug 889125 - Should remove rhc-chk in rhc client of Enterprise
Summary: Should remove rhc-chk in rhc client of Enterprise
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: oc
Version: 1.1.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: ---
Assignee: Brenton Leanhardt
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-20 09:55 UTC by Gaoyun Pei
Modified: 2017-03-08 17:34 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-01-31 20:33:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2013:0220 0 normal SHIPPED_LIVE Important: Red Hat OpenShift Enterprise 1.1 update 2013-02-01 01:23:24 UTC

Description Gaoyun Pei 2012-12-20 09:55:46 UTC
Description of problem:
Run $ rhc-chk, the CLI returns failure. 
As comment 11 metioned in https://bugzilla.redhat.com/show_bug.cgi?id=865391
" 'rhc chk' is in turn hitting the non-rest API. In On-Premise we only support the rest API."
So we should remove rhc-chk command in our rhc client.

Version-Release number of selected component (if applicable):
rhc-1.3.2
http://buildvm-devops.usersys.redhat.com/puddle/build/OpenShiftEnterprise/1.1.x/2012-12-19.2/

How reproducible:
Always

Steps to Reproduce:
1. eval `ssh-agent`
2. ssh-add ~/.ssh/id_rsa
3. rhc-chk

Actual results:
[jenkins2@openshift workwork]$ rhc-chk
Password: ******

Analyzing system
.EF..FF
=================================================
||  Your system did not pass all of the tests  ||
=================================================
1) You need to be able to connect to the server in order to test authentication.
2) You must have an account on the server in order to test: whether your local SSH keys match the ones in your account.
3) You must have an account on the server in order to test: connecting to your applications.

=========================================================
||  Something went wrong, and not all tests completed  ||
=========================================================
1) test_connectivity(Test1_Connectivity):
	RHC::Vendor::OkJson::Error: invalid character at "<!DOCTYPE "
	    /usr/lib/ruby/gems/1.8/gems/rhc-1.3.2/lib/rhc/vendor/okjson.rb:179:in `lex'
	    /usr/lib/ruby/gems/1.8/gems/rhc-1.3.2/lib/rhc/vendor/okjson.rb:45:in `decode'
	    /usr/lib/ruby/gems/1.8/gems/rhc-1.3.2/lib/rhc/json.rb:9:in `decode'
	    /usr/lib/ruby/gems/1.8/gems/rhc-1.3.2/lib/rhc-common.rb:101:in `json_decode'
	    /usr/lib/ruby/gems/1.8/gems/rhc-1.3.2/bin/rhc-chk:167:in `fetch_url_json'
	    /usr/lib/ruby/gems/1.8/gems/rhc-1.3.2/bin/rhc-chk:275:in `test_connectivity'

Expected results:

Additional info:

Comment 2 Brenton Leanhardt 2012-12-20 13:40:23 UTC
This will ship in the next puddle.

Comment 3 Gaoyun Pei 2012-12-21 03:35:30 UTC
Verify this bug against the new puddle:
http://buildvm-devops.usersys.redhat.com/puddle/build/OpenShiftEnterprise/1.1.x/2012-12-20.1/
rhc-1.3.2 from http://buildvm-devops.usersys.redhat.com/puddle/build/OpenShiftEnterprise/1.1.x/2012-12-20.1/Client/x86_64/os/Packages/

[root@slave1-onpremise-testing ~]# rhc-chk
bash: rhc-chk: command not found

Comment 5 errata-xmlrpc 2013-01-31 20:33:59 UTC
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/RHSA-2013-0220.html


Note You need to log in before you can comment on or make changes to this bug.