Poll Geo secondary node readiness API in QA tests
What does this MR do?
This merge requests implements Geo secondary node readiness API /-/readiness
polling instead of using sleep 90
in end-to-end Geo tests.
We need to wait for services on the secondary to start properly after setting up database replication, before starting tests.
Are there points in the code the reviewer needs to double check?
Does this MR meet the acceptance criteria?
-
Has been reviewed by a Backend maintainer -
End-to-end tests pass ( package-and-qa
manual pipeline job)
What are the relevant issue numbers?
Closes gitlab-org/gitlab-ee#6514
Edited by Grzegorz Bizon