action #111971
closed[security] wget_ipv6: www.zq1.de returns error 503
0%
Description
Observation¶
The server used to test wget (www.zq1.de) currently returns error 503 (no server available)
Not much we can do from our side, I'm afraid - but we need to track it (and if no solution happens on that server, use a different target server)
openQA test in scenario opensuse-Tumbleweed-JeOS-for-kvm-and-xen-x86_64-jeos-extra@64bit_virtio-2G fails in
wget_ipv6
Test suite description¶
Same as jeos, plus some more tests.
Reproducible¶
Fails since (at least) Build 20210824
Expected result¶
Last good: 20210823 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by okurz almost 2 years ago
- Subject changed from wget_ipv6: www.zq1.de returns error 503 to [security] wget_ipv6: www.zq1.de returns error 503
We could just use http://static.opensuse.org/favicon.ico instead. The test says it would test fallback from IPv6 to IPv4 but we don't ensure this and I don't think it even does this anymore. www3.zq1.de resolves to 2a01:4f8:221:b52::2 . I doubt we would actually fallback to IPv4. And we already have tests/console/wget_https.pm that does more. I think we can simply ditch this test module and replace by wget_https.pm which so far is used within the scope of "security" tests.
@security I suggest to replace all uses of wget_ipv6.pm with wget_https.pm and delete wget_ipv6.pm, agreed?
Updated by rfan1 almost 2 years ago
Hi @okurz,
Thanks for the comments, and I agree with you tests/console/wget_https.pm can cover wget function as well.
However, the issue can't be seen in the latest build 20220605.
It is fine for any job re-use the test module wget_https.pm, we can add more functions there if any requirements :)
Updated by rfan1 almost 2 years ago
Could we close this ticket now？ since it can't be reproduced :)
Updated by dimstar almost 2 years ago
- Status changed from New to Resolved
rfan1 wrote:
Could we close this ticket now？ since it can't be reproduced :)
Considering that this server rarely caused that issue, I think we are ok to stick to it. If it starts failing our tests too often we should switch to a test server under our control