Bug 801706 - should show exposed port number after expose-port via rhc client
Summary: should show exposed port number after expose-port via rhc client
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OKD
Classification: Red Hat
Component: oc
Version: 1.x
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Rob Millner
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-09 08:36 UTC by Meng Bo
Modified: 2013-11-18 00:38 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-19 18:23:07 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Meng Bo 2012-03-09 08:36:50 UTC
Description of problem:
when executing 'rhc-ctl-app -c expose-port' command, it only return success without any detail info.

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

How reproducible:
always

Steps to Reproduce:
1.create an app
#rhc app create -a testapp -t php-5.3
2.try to expose port of this app
#rhc-ctl-app -a testapp -c expose-port
3.
  
Actual results:
[bmeng@localhost ~]$ rhc-ctl-app -a test1 -c expose-port

RESULT:
Success


Expected results:
should contain the exposed port number in the output


Additional info:

Comment 1 Rob Millner 2012-03-12 18:17:57 UTC
The return values from expose and show-port are not being parsed by the API and setup behind the scenes as part of scaling.  These commands were exposed for testing and aren't needed any more.

commit c4b65c9 in li
commit 6742a5b in os_client_utils

Comment 2 Meng Bo 2012-03-13 05:04:08 UTC
checked on devenv_1659,
the expose-port command has been removed from client side.
mark bug as verified.


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