Skip to content

Draft: Bypass zoekt specs on dev temporarily

Mark Lapierre requested to merge ml-bypass-zoekt into master

What does this MR do and why?

In gitlab-com/gl-infra/production#15901 (closed) we ran into an issue with Zoekt specs failing on dev.gitlab.org. Our investigation (mostly in #incident-15901 on Slack) seemed to suggest that firstly webmock didn't like the ipv6 address and secondly that we couldn't connect with the address once we allowed it in webmock. We tried 2 other fixes before deciding the quickest solution was to just disable these specs in dev.gitlab.org since they seem to work fine on GitLab.com

  1. Firstly we saw webmock blocking requests which we seemed to successfully work around by mocking the ipv6 address with square brackets around it !124250 (d46a0bab) 
    Real HTTP connections are disabled. Unregistered request: POST http://[fc00::242:ac11:7]:6060/indexer/truncate with headers {'Accept'=>'*/*', 'Accept-Encoding'=>'gzip;q=1.0,deflate;q=0.6,identity;q=0.3', 'User-Agent'=>'Ruby'}
  2. Then after we got past webmock we ran into the requests failing to connect to Zoekt so we tried to workaround that by reverting !122308 (merged) but it still didn't seem to fix the issue. 
    Failed to open TCP connection to fc00::242:ac11:7:6060 (No route to host - connect(2) for "fc00::242:ac11:7" port 6060)

These efforts were in this MR https://dev.gitlab.org/gitlab/gitlab-ee/-/merge_requests/1553 which we couldn't get to pass.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before After

How to set up and validate locally

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Dylan Griffith

Merge request reports