Bug 999085

Summary:	oo-app-state-show calls "get_app_state" on OpenShift::ApplicationContainer
Product:	OpenShift Container Platform	Reporter:	Brenton Leanhardt <bleanhar>
Component:	Containers	Assignee:	Brenton Leanhardt <bleanhar>
Status:	CLOSED ERRATA	QA Contact:	libra bugs <libra-bugs>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	1.2.0	CC:	baulakh, gpei, libra-onpremise-devel, mmasters
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	The oo-app-state-show command used a deprecated API and caused an error. This issue has been fixed in the current release, and the oo-app-state-show command now uses the new API and works correctly.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-09-05 13:24:33 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:

Description Brenton Leanhardt 2013-08-20 17:43:36 UTC

Description of problem:
It should instead call "container.state.value"

How reproducible:


Steps to Reproduce:
1. Create a gear
2. oo-app-state-show --with-container-uuid $UUID --with-app-uuid $UUID

Actual results:
undefined method `get_app_state' for #<OpenShift::ApplicationContainer:0x000000021f3ec8>
[root@broker ~]# which aoo-app-state-show

Expected results:
The gear state should be shown.

Comment 1 Miciah Dashiel Butler Masters 2013-08-20 17:46:12 UTC

It's been fixed in Origin:   https://github.com/openshift/origin-server/commit/10aaec7a0ab35c2246f1f7e005952fd9a470ca34#L30L99

But I think we can just remove oo-app-state-show.  Is there any reason to keep it?

Comment 2 Miciah Dashiel Butler Masters 2013-08-20 17:46:59 UTC

Wrong link, sorry.  Here's the fix:   https://github.com/openshift/origin-server/commit/d978c3b9e14d864a35d56714813dffedee13d3a4

Comment 5 Gaoyun Pei 2013-08-21 05:31:37 UTC

Verify this on puddle: 1.2/2013-08-20.1

Create an app, and check its state by oo-app-state-show
[root@node ~]# oo-app-state-show --with-app-uuid 5214256d7074f5201a00045d --with-container-uuid 5214256d7074f5201a00045d
started[root@node ~]#

Stop the app, check again 
[root@node ~]# oo-app-state-show --with-app-uuid 5214256d7074f5201a00045d --with-container-uuid 5214256d7074f5201a00045d
stopped[root@node ~]# 

Idle the app
[root@node ~]# oo-app-state-show --with-app-uuid 5214256d7074f5201a00045d --with-container-uuid 5214256d7074f5201a00045d
idle[root@node ~]#

Comment 8 errata-xmlrpc 2013-09-05 13:24:33 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/RHBA-2013-1211.html