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
Plugins: Removing plugin does not fail when plugin dir is read only #6546
Labels
Comments
dadoonet
added a commit
to dadoonet/elasticsearch
that referenced
this issue
Jul 4, 2014
If you try to remove a plugin in read only dir, you get a successful result: ``` $ bin/plugin --remove marvel -> Removing marvel Removed marvel ``` But actually the plugin has not been removed. When installing, if fails properly: ``` $ bin/plugin -i elasticsearch/marvel/latest -> Installing elasticsearch/marvel/latest... Failed to install elasticsearch/marvel/latest, reason: plugin directory /usr/local/elasticsearch/plugins is read only ``` This change throw an exception when we don't succeed removing the plugin. Closes elastic#6546.
dadoonet
added a commit
that referenced
this issue
Jul 4, 2014
If you try to remove a plugin in read only dir, you get a successful result: ``` $ bin/plugin --remove marvel -> Removing marvel Removed marvel ``` But actually the plugin has not been removed. When installing, if fails properly: ``` $ bin/plugin -i elasticsearch/marvel/latest -> Installing elasticsearch/marvel/latest... Failed to install elasticsearch/marvel/latest, reason: plugin directory /usr/local/elasticsearch/plugins is read only ``` This change throw an exception when we don't succeed removing the plugin. Closes #6546. (cherry picked from commit 078cbf3)
dadoonet
added a commit
that referenced
this issue
Jul 4, 2014
If you try to remove a plugin in read only dir, you get a successful result: ``` $ bin/plugin --remove marvel -> Removing marvel Removed marvel ``` But actually the plugin has not been removed. When installing, if fails properly: ``` $ bin/plugin -i elasticsearch/marvel/latest -> Installing elasticsearch/marvel/latest... Failed to install elasticsearch/marvel/latest, reason: plugin directory /usr/local/elasticsearch/plugins is read only ``` This change throw an exception when we don't succeed removing the plugin. Closes #6546. (cherry picked from commit 078cbf3)
clintongormley
changed the title
Removing plugin does not fail when plugin dir is read only
Plugins: Removing plugin does not fail when plugin dir is read only
Jul 16, 2014
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
If you try to remove a plugin in read only dir, you get a successful result: ``` $ bin/plugin --remove marvel -> Removing marvel Removed marvel ``` But actually the plugin has not been removed. When installing, if fails properly: ``` $ bin/plugin -i elasticsearch/marvel/latest -> Installing elasticsearch/marvel/latest... Failed to install elasticsearch/marvel/latest, reason: plugin directory /usr/local/elasticsearch/plugins is read only ``` This change throw an exception when we don't succeed removing the plugin. Closes elastic#6546. (cherry picked from commit 078cbf3)
You could list your plugins with "plugin list". |
To uninstall Marvel: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If you try to remove a plugin in read only dir, you get a successful result:
But actually the plugin has not been removed.
When installing, if fails properly:
The text was updated successfully, but these errors were encountered: