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.
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?
Wrong link, sorry. Here's the fix: https://github.com/openshift/origin-server/commit/d978c3b9e14d864a35d56714813dffedee13d3a4
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 ~]#
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