[ML] Inconsistent behavior if no ML nodes are found

[sophiec20]

Found in 7.1.0 "build_hash" : "606a173", "build_date" : "2019-05-16T00:43:15.323135Z",

In Cloud, if there are no ML nodes the following is allowed:

• Settings / filter list CRUD
• Data Viz / Import Data
• Data Viz / Select index pattern - but does not go as far as to view the data vizualiser for it

The following is redirected to the Job Management page with a message No ML nodes available There are no ML nodes available. You will not be able to create or run jobs.

• Create Job
• View Data Visualizer page

The following is disabled:

• Settings / Calendar management CRUD

To give consistent behaviour if there are no ML nodes.. suggest the following

In Data Visualizer

• Allow import data
• Allow data visualizer to display (but redirect if Create job is selected)

Redirect to the No ML Nodes message upon

• Create job

In Settings, disable ability to CRUD calendars and filters and provide a message to explain why this is disabled.

Note: The above was found on 7.1 and may since have changed. Also, would need to think through what the behaviour is if jobs were created when ML nodes existed but had since been removed. If this is possible, then "start" jobs would also need to be disabled.

[elasticmachine]

Pinging @elastic/ml-ui (:ml)