Need to ensure upstream fix gets into Enterprise. +++ This bug was initially created as a clone of Bug #977519 +++ Description of problem: When a user adds a downloadable cartridge with malformed YAML to an app, the broker returns an ISE on all subsequent calls. How reproducible: Always Steps to Reproduce: 1. rhc app create dlcart jbossas-7 2. rhc cartridge add https://raw.github.com/Tok/OpenShift-IRC-cartridge/master/metadata/manifest.yml 3. Try to use the web console or any rhc commands. Actual results: rhc returns "The server did not respond correctly." The web console shows "We appear to be having technical difficulties" Expected results: The broker should handle exceptions. The cartridge addition should fail, or the user should be able to remove it to get back into a working state.
https://github.com/openshift/enterprise-server/pull/107 Fix CPed from origin-server origin stage commit a6cb4f474fde8fb8930f097eb6ed428b9783f468 origin master commit 4a7c640248f238d59e1304e526b3f92383fb7c3f However, note that it won't fix an application that is already broken in this way. For that, you pretty much need to force-destroy it administratively, e.g.: # oo-admin-ctl-app --command force-destroy -l demo -a boom
There was a follow-on fix upstream at https://github.com/openshift/origin-server/pull/3068 but the code has already drifted enough that I think pulling that in would be overly complicated/risky. That was not as urgent a problem as the one solved above.
Verify this bug on puddle 1.2/2013-07-18.4 1. create an app rhc app create app1 ruby-1.8 2. add a malformed mysql cartridge to the application [root@dhcp-8-133 workspace]# rhc cartridge add https://raw.github.com/jhou1/downloadable-malformed/master/metadata/manifest.yml -a app1 The cartridge 'https://raw.github.com/jhou1/downloadable-malformed/master/metadata/manifest.yml' will be downloaded and installed Adding https://raw.github.com/jhou1/downloadable-malformed/master/metadata/manifest.yml to application 'app1' ... can't convert nil into String
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-1138.html