Wait for elasticsearch to be green on install
What does this MR do?
From #197230 (closed) and also identified in #34537 (closed)
We should wait for Elastic Search to actually be available before marking the app as "installed". This reduces confusion of a user immediately navigating to logs and seeing an error page.
It also turns out that our ES clusters were never in a green health status, because we were only launching 1 data nodes. Bumping the data nodes to 2 makes the cluster happy.
Screenshots
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team