Kibana: User shouldn't be allowed to delete .kibana index through index management.

Created on 9 Apr 2019 · 5Comments · Source: elastic/kibana

Kibana version: 7.0.0 BC2

Elasticsearch version: 7.0.0 BC2

Server OS version: darwin_x86_64

Browser version: chrome latest

Browser OS version: OS X

Original install method (e.g. download page, yum, from source, etc.): from staging

Describe the bug: Current implementation lets the user delete .kibana index from the index management UI. This makes the UI go kaput. User needs to restart to ensure .kibana index gets created again.

This needs to be addressed so user cannot delete the .kibana index.

Kibana logs:

Debug: internal, implementation, error 
    Error: handler method did not return a value, a promise, or throw an error
    at module.exports.internals.Manager.execute (/Users/bhavyarajumandya/Desktop/kibana_starting_conditions/kibana-7.0.0-darwin-x86_64/node_modules/hapi/lib/toolkit.js:52:29)
 error  [08:19:53.447]  Error: handler method did not return a value, a promise, or throw an error
    at module.exports.internals.Manager.execute (/Users/bhavyarajumandya/Desktop/kibana_starting_conditions/kibana-7.0.0-darwin-x86_64/node_modules/hapi/lib/toolkit.js:52:29)
Debug: internal, implementation, error 
    Error: handler method did not return a value, a promise, or throw an error
    at module.exports.internals.Manager.execute (/Users/bhavyarajumandya/Desktop/kibana_starting_conditions/kibana-7.0.0-darwin-x86_64/node_modules/hapi/lib/toolkit.js:52:29)
 error  [08:20:01.552]  Error: handler method did not return a value, a promise, or throw an error
    at module.exports.internals.Manager.execute (/Users/bhavyarajumandya/Desktop/kibana_starting_conditions/kibana-7.0.0-darwin-x86_64/node_modules/hapi/lib/toolkit.js:52:29)
Debug: internal, implementation, error 
    Error: handler method did not return a value, a promise, or throw an error
    at module.exports.internals.Manager.execute (/Users/bhavyarajumandya/Desktop/kibana_starting_conditions/kibana-7.0.0-darwin-x86_64/node_modules/hapi/lib/toolkit.js:52:29)
 error  [08:20:23.444]  Error: handler method did not return a value, a promise, or throw an error
    at module.exports.internals.Manager.execute (/Users/bhavyarajumandya/Desktop/kibana_starting_conditions/kibana-7.0.0-darwin-x86_64/node_modules/hapi/lib/toolkit.js:52:29)
  log   [08:20:26.032] [error][spaces] Unable to navigate to space "default", redirecting to Space Selector. Error: Saved object [space/default] not found
  log   [08:20:26.044] [error][spaces] Unable to navigate to space "default", redirecting to Space Selector. Error: Saved object [space/default] not found
  log   [08:20:26.059] [error][spaces] Unable to navigate to space "default", redirecting to Space Selector. Error: Saved object [space/default] not found

Index Management Elasticsearch UI bug

Source

bhavyarm

Most helpful comment

I think we should help the user avoid shooting themselves in the foot, but I feel like preventing the user from using the UI to do something that they could do via other means is too helicopter-parenty. As an alternative, I'd suggest throwing up a confirmation modal with a blatant warning: "You will break Kibana by doing this. Are you sure this is what you want to do?" And the confirmation options are: "No, keep Kibana working" and "Yes, break Kibana".