-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unrecognized import path error in Py Integration tests #43044
Comments
Compared @shmsr found the related issue was found: aws/aws-k8s-tester#577 (comment). Which pointed that there might be some DNS issue; because port is 53 (127.0.0.53:53). Related PR with problem debug: #43084
In VM:
So, using 8.8.8.8 also did not work. |
Found that core images for Ubuntu 2204 were failing since Wed 12th Feb: https://buildkite.com/elastic/ci-vm-images/builds/8546, and fails up to this date. Will try to add CoreDns to and image. Added CoreDns with Google address 8.8.8.8 - which resulted in a same error: https://buildkite.com/elastic/beats-xpack-metricbeat/builds/12536#01956c6a-75c4-47c6-9a98-f8520ca9ea29/126-391 Potentially relevant issue was found in |
On March 3 - no issue is detected while running PyInt tests on a default beats image: https://buildkite.com/elastic/beats-xpack-metricbeat/builds?branch=debug-go-imports Beats Ubuntu 2204 was last successfully built on Feb 27: https://buildkite.com/elastic/vm-images-platform-ingest/builds/557#01954522-c485-4494-b164-cc734a272b56 Since the error is not currently reproduced, it's barely possible to make any researches and changes. |
Discovered while backporting #42825 on Feb 24. Backports to 8.16 and 8.17 for (x-pack/)metricbeat were failing with
module/mongodb/mongodb.go:27:2: unrecognized import path "go.mongodb.org/mongo-driver": https fetch: Get "https://go.mongodb.org/mongo-driver?go-get=1": dial tcp: lookup go.mongodb.org on 127.0.0.53:53: no such host
.During analysis, it was discovered that these errors started occurring since Feb 14 on base 8.16 and Feb 17 on base 8.17:
8.16: https://buildkite.com/elastic/beats-metricbeat/builds/13988#019505f4-9df4-4e14-bca0-29ec89fcc370/112-322
8.17: https://buildkite.com/elastic/beats-xpack-metricbeat/builds/11665#0195137d-710d-4390-bdc9-b2cca3d28ea3/105-370
What was tried:
After triggering builds - some tests succeeded, some failed again. After triggering retries, those were successful/failing without any pattern.
dig go.mongodb.org
andservice systemd-resolved status
commands tox-pack/metricbeat: Python Integration Tests (Module)
: https://buildkite.com/elastic/beats-xpack-metricbeat/builds/12049#01953e84-c117-47b4-924f-b9db384580f8/144-151Based on
dig
output DNS query completed without errors. The authority showed thatns-cloud-c1.googledomains.com
is authoritative for themongodb.org
, which might be the problem root-cause, but no proof here.systemd-resolved
seems to be working as expected.3. Compared mongo.db and other dependency versions with 8.17 and 8.x, which didn't show any differences that could affect the behaviour.
4. Retried failed steps for multiple times, and occasionally tests were successful. The next day the problem was not detected on 8.16 and 8.17 base branches.
Need to mention, that 8.18 and 8.x didn't face the issue with import path, so the problem with beats image itself can be excluded.
The text was updated successfully, but these errors were encountered: