Bug 1097724 - Broker should give meaningful error messages at failed attempts to create an app
Summary: Broker should give meaningful error messages at failed attempts to create an app
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OKD
Classification: Red Hat
Component: Pod
Version: 2.x
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Abhishek Gupta
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-14 12:13 UTC by Oleg Fayans
Modified: 2017-05-31 18:22 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-05-31 18:22:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
mcollective log. search for the "ulala" keyword (1.78 MB, text/x-log)
2014-05-14 12:13 UTC, Oleg Fayans
no flags Details

Description Oleg Fayans 2014-05-14 12:13:39 UTC
Created attachment 895470 [details]
mcollective log. search for the "ulala" keyword

Description of problem:

When I am trying to create an app with a custom misconfigured cartridge, the server throws the following error:

$ rhc app create ulala shiny-1.1
Application Options
-------------------
Domain:     mhjdhy
Cartridges: shiny-1.1
Gear Size:  default
Scaling:    no

Creating application 'ulala' ... 
Unable to complete the requested operation due to: An invalid exit code (1) was returned from the server localhost.localdomain.  This indicates an unexpected problem during the execution of
your request..
Reference ID: 1dc65c21848ecf5fceffbad5ebddb205

The logs on the server also do not contain any meaningful information (the full mcollective log is attached):


I, [2014-05-14T06:29:43.779394 #8708]  INFO -- : openshift.rb:93:in `cartridge_do_action' cartridge_do_action validation = shiny-1.1 post-configure {"--with-app-uuid"=>"53734590e13823105f000
01c", "--with-app-name"=>"ulala", "--with-container-uuid"=>"53734590e13823105f00001c", "--with-container-name"=>"ulala", "--with-namespace"=>"mhjdhy", "--with-request-id"=>"1dc65c21848ecf5fc
effbad5ebddb205", "--cart-name"=>"shiny-1.1", "--component-name"=>"shiny-1.1", "--with-software-version"=>"1.1", "--cartridge-vendor"=>"redhat"}
I, [2014-05-14T06:29:43.779549 #8708]  INFO -- : openshift.rb:134:in `execute_action' Executing action [post-configure] using method oo_post_configure with args [{"--with-app-uuid"=>"5373459
0e13823105f00001c", "--with-app-name"=>"ulala", "--with-container-uuid"=>"53734590e13823105f00001c", "--with-container-name"=>"ulala", "--with-namespace"=>"mhjdhy", "--with-request-id"=>"1dc
65c21848ecf5fceffbad5ebddb205", "--cart-name"=>"shiny-1.1", "--component-name"=>"shiny-1.1", "--with-software-version"=>"1.1", "--cartridge-vendor"=>"redhat"}]
E, [2014-05-14T06:29:44.125962 #8708] ERROR -- : openshift.rb:313:in `rescue in with_container_from_args' No such file or directory - chdir
E, [2014-05-14T06:29:44.126073 #8708] ERROR -- : openshift.rb:314:in `rescue in with_container_from_args' /usr/share/gems/gems/openshift-origin-node-1.18.0.1/lib/openshift-origin-node/utils/shell_exec.rb:116:in `spawn'




Version-Release number of selected component (if applicable):

# rpm -qa | grep broker
openshift-origin-broker-1.15.1.2-1.fc19.noarch
rubygem-openshift-origin-msg-broker-mcollective-1.18.0.1-1.fc19.noarch
openshift-origin-broker-util-1.18.0.1-1.fc19.noarch

How reproducible:

always

Steps to Reproduce:
1. Install Origin on CentOS 6.5, or RHEL 6.5 and ssh to it
2. yum install R -y
3. R -e "install.packages('shiny', repos='http://cran.rstudio.com/')"
4. wget http://download3.rstudio.org/centos-6.3/x86_64/shiny-server-1.1.0.49-x86_64.rpm
5. yum install --nogpgcheck shiny-server-1.1.0.49-x86_64.rpm
6. cp /opt/shiny-server/config/init.d/redhat/shiny-server /etc/init.d/
7. chkconfig --level 345 shiny-server on
8. git clone git:ofayans/shiny_cartridge.git
9. oo-admin-cartridge -a install -s shiny_cartridge
10. rhc cartridge list - should give you shiny-1.1 among others
11. rhc app create mynewapp shiny-1.1

Actual results:
The last step pukes with meaningless error message not helping to debug at all

Expected results:
Should give something like "You are missing bin/control script in your cartridge"

Additional info:

Comment 2 Eric Paris 2017-05-31 18:22:11 UTC
We apologize, however, we do not plan to address this report at this time. The majority of our active development is for the v3 version of OpenShift. If you would like for Red Hat to reconsider this decision, please reach out to your support representative. We are very sorry for any inconvenience this may cause.


Note You need to log in before you can comment on or make changes to this bug.