Opened on behalf of a user on IRC: rhc create-app --debug comma jbosseap-6.0 mysql-5.1 --from-code https://github.com/Athou/commafeed.git 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: 12cf6d211be82d51c7acb47eae347d4e Was exactly 180s, so something failed on the node side. Please investigate
Initial debugging yielded: 2013-05-16 10:26:03.591 [ERROR] Reference ID: 12cf6d211be82d51c7acb47eae347d4e - Node execution failure (invalid exit code from node). If the problem persists please contact Red Hat support. /opt/rh/ruby193/root/usr/share/gems/gems/openshift-origin-msg-broker-mcollective-1.8.6/lib/openshift/mcollective_application_container_proxy.rb:2639:in `parse_result' /opt/rh/ruby193/root/usr/share/gems/gems/openshift-origin-msg-broker-mcollective-1.8.6/lib/openshift/mcollective_application_container_proxy.rb:2787:in `run_cartridge_command' /var/www/openshift/broker/lib/online/broker/mcollective_ext.rb:13:in `run_cartridge_command' /opt/rh/ruby193/root/usr/share/gems/gems/openshift-origin-msg-broker-mcollective-1.8.6/lib/openshift/mcollective_application_container_proxy.rb:753:in `post_configure_cartridge' /opt/rh/ruby193/root/usr/share/gems/gems/openshift-origin-controller-1.8.11/app/models/gear.rb:140:in `post_configure_component' /opt/rh/ruby193/root/usr/share/gems/gems/openshift-origin-controller-1.8.11/app/models/pending_app_op_group.rb:195:in `block in execute' /opt/rh/ruby193/root/usr/share/gems/gems/openshift-origin-controller-1.8.11/app/models/pending_app_op_group.rb:154:in `each' /opt/rh/ruby193/root/usr/share/gems/gems/openshift-origin-controller-1.8.11/app/models/pending_app_op_group.rb:154:in `execute' /opt/rh/ruby193/root/usr/share/gems/gems/openshift-origin-controller-1.8.11/app/models/application.rb:1255:in `run_jobs' /opt/rh/ruby193/root/usr/share/gems/gems/openshift-origin-controller-1.8.11/app/models/application.rb:497:in `block in add_features' /opt/rh/ruby193/root/usr/share/gems/gems/openshift-origin-controller-1.8.11/app/models/application.rb:1297:in `run_in_application_lock' /opt/rh/ruby193/root/usr/share/gems/gems/openshift-origin-controller-1.8.11/app/models/application.rb:495:in `add_features' /opt/rh/ruby193/root/usr/share/gems/gems/openshift-origin-controller-1.8.11/app/models/application.rb:175:in `create_app' /opt/rh/ruby193/root/usr/share/gems/gems/openshift-origin-controller-1.8.11/app/controllers/applications_controller.rb:94:in `create' /opt/rh/ruby193/root/usr/share/gems/gems/actionpack-3.2.8/lib/action_controller/metal/implicit_render.rb:4:in `send_action' Don't have the corresponding node issue, transferring to broker
Thomas McGonagle is the ops runner on these
This is a timeout issue. The mcollective timeout on my devenv was 240s and post-configure (postreceive on the node side) step failed to complete. The timeout failure triggered a rollback of the application from the broker side. We can either further increase the timeout or handle timeout errors on the broker side differently.
This is a current limitation of the way things are implemented currently. When using --from-code to create applications, it is important to ensure that create/build/start complete in under 4 minutes so as not to trigger a timeout and an automatic rollback. In the short-term (), for quickstarts that take longer to configure/setup, the workaround is to create the application with the required components and then add the code later (add a remote git repo) and do a git push. In the mid-to-long term we would like to consider executing such tasks using a scheduler that is either not impacted by timeouts or handles timeout situations better instead of simply doing a rollback. Lowering severity to low since we have a workaround.
*** Bug 966731 has been marked as a duplicate of this bug. ***
*** Bug 985547 has been marked as a duplicate of this bug. ***
Closing as upstream based on this trello card: https://trello.com/c/MHHm33bz