IPv6 [sig-network] wget command error

[cloudgrimm]

[provide a description of the issue]
[sig-network] services when using a plugin that does not isolate namespaces by default should allow connections to pods in different namespaces on different nodes via service IPs [Suite:openshift/conformance/parallel] fails with wget command terminated with exit code 1

Version

[provide output of the openshift version or oc version command]
Client Version: 4.7.0-0.nightly-2021-03-14-223051
Server Version: 4.7.0-0.nightly-2021-03-14-223051
Kubernetes Version: v1.20.0+bafe72f

Steps To Reproduce

1. Download this repo and run ./openshift-tests run openshift/conformance/parallel

Current Result

`fail [github.com/openshift/origin/test/extended/networking/services.go:33]: Expected success, but got an error:
<exec.CodeExitError>: {
Err: {
s: "error running /usr/local/bin/kubectl --server=SERVER --kubeconfig=KUBECONFIG --namespace=e2e-net-services2-4338 exec execpod-sourceip-openshift-worker -- /bin/sh -x -c wget -T 30 -qO- fd02::7082:8080:\nCommand stdout:\n\nstderr:\n+ wget -T 30 -qO- fd02::7082:8080\nwget: can't connect to remote host: Network unreachable\ncommand terminated with exit code 1\n\nerror:\nexit status 1",
},
Code: 1,
}
error running /usr/local/bin/kubectl --server=SERVER --kubeconfig=/KUBECONFIG --namespace=e2e-net-services2-4338 exec execpod-sourceip-openshift-worker -- /bin/sh -x -c wget -T 30 -qO- fd02::7082:8080:
Command stdout:

stderr:
+ wget -T 30 -qO- fd02::7082:8080
wget: can't connect to remote host: Network unreachable
command terminated with exit code 1

error:
exit status 1`

Expected Result

• Passed test

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[cloudgrimm]

/remove-lifecycle stale

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.