Bug 860939 - [fork] Cartridge properties are shown empty {} while using rhc cartridge status
Summary: [fork] Cartridge properties are shown empty {} while using rhc cartridge status
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OKD
Classification: Red Hat
Component: oc
Version: 2.x
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Clayton Coleman
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-27 07:04 UTC by joycezhang
Modified: 2015-05-15 02:05 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-10-04 15:06:19 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description joycezhang 2012-09-27 07:04:14 UTC
Description of problem:
Empty cartridge properties are shown while using rhc cartridge status as below:

# rhc cartridge status postgresql-8.4 -a php1
Password: *

--DEBUG--

--RESULT--
PostgreSQL server instance is running

--MESSAGE--

--ERROR--

--APP INFO--

--CART COMMANDS--

--CART PROPERTIES--
{}
--DATA--

--EXIT CODE--
0


Version-Release number of selected component (if applicable):
fork_ami_US2597_US2599_US2813_US2817_US2872_172 (ami-735fed1a)

How reproducible:
always

Steps to Reproduce:
1.Create an app
2.Add cartridge to this app:
rhc cartridge add postgresql-8.1 -a php1 -p xx
3.Check cartridge staus:
# rhc cartridge status postgresql-8.4 -a php1
  
Actual results:
Cartridge properties are empty as below:
# rhc cartridge status postgresql-8.4 -a php1
Password: *

--DEBUG--

--RESULT--
PostgreSQL server instance is running

--MESSAGE--

--ERROR--

--APP INFO--

--CART COMMANDS--

--CART PROPERTIES--
{}
--DATA--

--EXIT CODE--
0


Expected results:
Useful cartridge properties are shown in "{ }" or CART PROPERTIES is hidden instead of an empty "{ }".


Additional info:

Comment 1 John (J5) Palmieri 2012-10-04 15:06:19 UTC
This is being fixed in another bug on the rest api.  Only the result string should be seen in the future.


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