chutney doesn't verify using IPv6 addresses

Even when chutney is using IPv6 exits, it doesn't give clients an IPv6 address to connect to when verifying.

When chutney is using IPv6 bridges, I don't know if it gives their IPv6 address to bridge clients.

This is a significant coverage gap that I think is easily fixed by slight modifications to the chutney templating and verification code.

added component::core tor/chutney ipv6 outreachy-ipv6 parent::17811 points::3 priority::high severity::normal status::assigned testing tor-tests-integration type::defect labels

To clarify, this most likely means that:

• the bridges are listening on IPv6, but the bridge clients are connective over IPv4
• the exits are willing to connect via IPv6, but never get an IPv6 request (but see #16971 (moved), an exit on a network where there is no IPv6 DNS may refuse IPv6 requests)

If we are trying to force IPv6-only exit connections, we need to stop the authorities being exits in #17090 (moved).

Trac:
Parent: #16949 (moved) to #17811 (moved)
Severity: N/A to Normal
Sponsor: N/A to N/A
Keywords: SponsorS testing deleted, SponsorS testing ipv6 added

Trac:
Sponsor: N/A to SponsorS-can
Keywords: SponsorS testing ipv6 deleted, SponsorS, tor-tests-integration, testing, ipv6 added

Trac:
Points: N/A to 3
Reviewer: N/A to N/A

Remove myself as chutney ticket owner. Default owners are trouble.

Trac:
Owner: nickm to N/A
Status: new to assigned

Trac:
Status: assigned to new

Trac:
Keywords: SponsorS deleted, outreachy-ipv6 added
Sponsor: SponsorS-can to N/A

Trac:
Owner: N/A to MrSquanchee
Status: new to assigned

We haven't selected a GSOC or Outreachy applicant yet.

To be fair to all applicants, we should only assign tickets to people who are actively working on that ticket.

Trac:
Owner: MrSquanchee to N/A

changed time estimate to 24h

mentioned in issue #17013 (moved)

mentioned in issue #17090 (moved)

mentioned in issue #17153 (moved)

mentioned in issue #17271 (moved)

mentioned in issue #17812 (moved)

mentioned in issue #17840 (moved)

mentioned in issue #17845 (moved)

mentioned in issue #20067 (moved)

mentioned in issue #20142 (moved)

mentioned in issue #21001 (moved)

mentioned in issue #26664 (moved)

mentioned in issue #30182 (moved)

mentioned in issue #31543 (moved)

moved to tpo/core/chutney#17011

mentioned in issue tpo/core/chutney#17013 (closed)

mentioned in issue tpo/core/chutney#17090 (closed)

mentioned in issue tpo/core/tor#17845 (closed)