New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
plugin script does not exit with exit code != 0 on error #3463
Labels
Comments
ghost
assigned s1monw
Aug 8, 2013
the output with the patch is:
|
s1monw
added a commit
to s1monw/elasticsearch
that referenced
this issue
Aug 8, 2013
We currently return with status code 0 when an IOException occurs. The plugin manager should in any case return a nonzero status if the operation was not successful. Now the PluginManager uses the following reponse codes based on 'sysexists.sh': * '0' on success * '64' command line usage error * '70' internal software error * '74' input/output Closes elastic#3463
Awesome, thanks a lot! |
s1monw
added a commit
that referenced
this issue
Aug 9, 2013
We currently return with status code 0 when an IOException occurs. The plugin manager should in any case return a nonzero status if the operation was not successful. Now the PluginManager uses the following reponse codes based on 'sysexists.sh': * '0' on success * '64' command line usage error * '70' internal software error * '74' input/output Closes #3463
This was referenced Aug 22, 2013
dadoonet
added a commit
to dadoonet/elasticsearch
that referenced
this issue
Sep 9, 2013
Now with have proper exit codes for elasticsearch plugin manager (see elastic#3463), we can add a silent mode to plugin manager. ```sh bin/plugin --install karmi/elasticsearch-paramedic --silent ``` Closes elastic#3628.
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
We currently return with status code 0 when an IOException occurs. The plugin manager should in any case return a nonzero status if the operation was not successful. Now the PluginManager uses the following reponse codes based on 'sysexists.sh': * '0' on success * '64' command line usage error * '70' internal software error * '74' input/output Closes elastic#3463
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
Now with have proper exit codes for elasticsearch plugin manager (see elastic#3463), we can add a silent mode to plugin manager. ```sh bin/plugin --install karmi/elasticsearch-paramedic --silent ``` Closes elastic#3628.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to reproduce:
Expected result: The exit code should be != 0
Actual result: The exit code is 0
The text was updated successfully, but these errors were encountered: