De-quarantine kubernetes test
What does this MR do?
De-quaranine the Kubernetes Agent QA test.
This spec started to fail consistently around Jan 5. Before this date, the test was passing consistently. So, on the Jan 11, the test got quarantined: !77942 (merged).
There were no spec changes to the test that I'm aware of, so I started to think this could be an environment related problem.
Also on Jan 5, we've made some changes to our gstg
infrastructure that impact how we route requests to KAS: gitlab-com/gl-infra/k8s-workloads/gitlab-com@bbe05743
From this day on, we had a few MRs that are related to our GitLab chart that also relates to how the requests are routed. See the comment here.
Test validation
Since a few days ago, this test seems to be consistently passing. We saw this on Allure reports:
- https://storage.googleapis.com/gitlab-qa-allure-reports/staging-full/master/index.html#suites/e31fabbab409ee42797cf955ed6573ff/a8a2f3655eb9ddb1/history
- https://storage.googleapis.com/gitlab-qa-allure-reports/staging-full/master/1034139/index.html#suites/e31fabbab409ee42797cf955ed6573ff/39d4a47a5e5c4e84/history
As well as on a couple of tests run by @niskhakova (internal slack thread)
I believe the test now passes after the recent fixes we did to our GitLab chart, as mentioned in the above comment.
Since, we couldn't find evidence of the test failing anymore this days, I'd like to suggest that we de-quarantine it, and watch how healthy it stays on the staging full-run.
E2E Test Failure issue(s)
#349708 (closed), #349705 (closed)
Check-list
-
General code guidelines check-list -
Quarantine test check-list -
Follow the Quarantining Tests guide. -
Confirm the test has a quarantine:
tag with the specified quarantine type. -
Note if the test should be quarantined for a specific environment. -
(Optionally) In case of an emergency (e.g. blocked deployments), consider adding labels to pick into auto-deploy (Pick into auto-deploy priority1 severity1).
-
-
Dequarantine test check-list -
Follow the Dequarantining Tests guide. -
Confirm the test consistently passes on the target GitLab environment(s). -
(Optionally) Trigger a manual GitLab-QA pipeline against a specific GitLab environment using the RELEASE
variable from thepackage-and-qa
job of the current merge request.
-
-
-
To ensure a faster turnaround, ask in the #quality
Slack channel for someone to review and merge the merge request, rather than assigning it directly.