test/librbd: use really invalid domain

[trociny]

in TestMockMigrationHttpClient.OpenResolveFail

"dne.invalid" seems to be a good choice as according to rfc2606:

".invalid" is intended for use in online construction of domain
names that are sure to be invalid and which it is obvious at a
glance are invalid.

[1] https://datatracker.ietf.org/doc/html/rfc2606#section-2

Fixes: https://tracker.ceph.com/issues/51342

Signed-off-by: Mykola Golub mgolub@suse.com

Checklist

• References tracker ticket
• Updates documentation if necessary
• Includes tests for new functionality or reproducer for bug

---

Show available Jenkins commands

• jenkins retest this please
• jenkins test classic perf
• jenkins test crimson perf
• jenkins test signed
• jenkins test make check
• jenkins test make check arm64
• jenkins test submodules
• jenkins test dashboard
• jenkins test api
• jenkins test docs
• jenkins render docs
• jenkins test ceph-volume all
• jenkins test ceph-volume tox

[trociny]

Hm, it is now fails on Jenkins with:

[ RUN      ] TestMockMigrationHttpClient.OpenResolveFail
../src/test/librbd/migration/test_mock_HttpClient.cc:348: Failure
Expected equality of these values:
  -2
  ctx.wait()
    Which is: -11
[  FAILED  ] TestMockMigrationHttpClient.OpenResolveFail (36 ms)

Although it passess for me locally.

[idryomov]

I think the one usually used is "foo.invalid", but "dne.invalid" of course works too.

[idryomov]

Hm, it is now fails on Jenkins with:

[ RUN      ] TestMockMigrationHttpClient.OpenResolveFail
../src/test/librbd/migration/test_mock_HttpClient.cc:348: Failure
Expected equality of these values:
  -2
  ctx.wait()
    Which is: -11
[  FAILED  ] TestMockMigrationHttpClient.OpenResolveFail (36 ms)

Although it passess for me locally.

I remember seeing /etc/hosts affecting such tests in the past...

[idryomov]

This is probably because on the jenkins node the response is SERVFAIL instead of NXDOMAIN. We might need to use a well-known domain with a garbage subdomain to ensure the expected NXDOMAIN response.

[tchaikov]

thank you @idryomov and @trociny for the quick fix and review! can we get this fix merged once the "make check" test passes?

[idryomov]

@trociny Let's switch to "foo.example", it appears to do the trick.

[trociny]

Changed to "foo.example". It seems to work on Jenkins indeed.