Update gitlab-qa to 15.10.2

Andrew Dunnrequested to merge
update-gitlab-qa-15.10.2 into master

What does this MR do?

This MR updates the gitlab-qa gem to 15.10.2. The airgapped E2E job still runs the 15.10.1 leak check, whose wget probe exits 0 whatever the fetch does. 15.10.2 carries the change that lets the probes fail.

15.10.2 is a patch release with one change, gitlab-qa!1477 (merged). Apart from the version files, it touches only the airgapped scenario, its spec and a passage of docs/what_tests_can_be_run.md. No scenario or CLI option changes, and the gem's runtime dependencies are the same as in 15.10.1.

  • After the firewall rules go in, the scenario now fails when gitlab.com port 443, example.com port 80 or 443, or dns.google port 53 is reachable.
  • It logs two lines that never fail the job: whether gitlab.com port 8080 is reachable, and how many packets the OUTPUT policy dropped.
  • Before the rules go in, it also needs example.com port 443 reachable, and example.com and dns.google resolvable.

Review notes

  • qa/Gemfile.lock has the new version and its checksum, the same shape as !265330 (merged). The checksum is the sha256 of the gem file on rubygems.org.
  • The airgapped job can now fail on a master pipeline if the sealing rules let one of those destinations through. That is the change working as intended.
  • The pipeline-common GITLAB_QA_VERSION is a separate pin that this MR leaves alone.

An AI coding assistant wrote this change. The assistant also compared the 15.10.1 and 15.10.2 tags of gitlab-qa, checked the new checksum against the gem file downloaded from rubygems.org, and compared the two versions' runtime dependency lists. It ran no CI job and no spec.

Related issues

Checklist

Pre-merge

Consider the effect of the changes in this merge request on the following:

Post-merge

Merge request reports