Hi, I'm attempting to create a new cartridge called 'jbpmengine' by initially leveraging the jbosseap cartridge (https://github.com/openshift/origin-server/tree/master/cartridges/openshift-origin-cartridge-jbosseap ). thus far i've followed along Clayton's cartridge 2.0 tutorial (https://www.openshift.com/blogs/introducing-the-openshift-cartridge-api-version-2 ..... excellent overview, by the way) and am executing this command : rhc create-app jbpmengine "http://cartreflect-claytondev.rhcloud.com/reflect?github=jbride/openshift-origin-cartridge-jbpm-engine&commit=master" i know the broker is doing a lot behind the scenes but in this case exits with the following response to my rhc client: Unable to complete the requested operation due to: Node execution failure (invalid exit code from node). If the problem persists please contact Red Hat support.. Reference ID: 8a1bcec071e9678567638a059cbb05b9 i suspect i've hosed something up in my cart but it's difficult to pinpoint the problem because the node provides little clues. thanks! jeff
The application creation is failing with something like: 2013-07-03 16:31:32.624 [DEBUG] DEBUG: server results: Failed to execute: 'control start' for /var/lib/openshift/4c0275aee41f11e2b5f512313b06d0b2/jbpmengine (pid:4472) I tracked this down to your malformed manifest.yml; you edited "Name:" element to 'jbpmengine', which caused disconnect between the cartridge scripts (including bin/control) and the various environment variables. This, in turn, caused 'ishttpup()' function to never succeed. Changing "Name:" back to 'jbosseap' should allow application to be created successfully. This should be documented in https://github.com/openshift/origin-server/blob/master/node/README.writing_cartridges.md but it is not. I created https://bugzilla.redhat.com/show_bug.cgi?id=981051 to further track that issue. In the meantime, you should be able to move forward. Let us know if you need further assistance.
The exact failure may be different, actually, not the environment variables issue that I described above. The cause, however, is the same: manifest.yml was internally inconsistent. We should improve our documentation.