Closed cuff-links closed 2 weeks ago
Pinging @elastic/kibana-stack-management (Team:Stack Management)
Pinging @elastic/kibana-management (Team:Kibana Management)
This is reported on an older version, so we will need to triage if still valid. In this case, we should be using the danger
callout. See: https://eui.elastic.co/#/display/callout#danger
I checked and this still happens. I'll fix it.
I'm wondering if we should also add a Max node connections validation when the number is introduced (not sure if we have that info or that complete depends on the backend). Probable will be better to open another issue if we decide to add the validation
@SoniaSanzV I agree that validation should be added as the error message in the screen shot isn't very helpful.
Summary
Environment
Kibana: 7.15.0 BC1 Elasticsearch 7.15.0 BC1 Browsers: All Browsers
Steps to reproduce:
1.) Navigate to Remote Clusters 2.) Create a new Remote Cluster 3.) Add information for a cluster except set the max number of connections to 999999999999999999 4.) Try to save.
Expected Result
The callout that shows the parsing error should be red with an alert icon.
Actual Result
The callout is yellow with an x icon. (See Image)