-
Notifications
You must be signed in to change notification settings - Fork 91
broadly investigate the NFT errors on ipv6 #472
Comments
/help-needed |
Run the test_e2e.sh script locally with nft backend and IPv6 set, use GINKGO_FOCUS with one the SKIPPED test for example |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close not-planned |
@k8s-triage-robot: Closing this issue, marking it as "Not Planned". In response to this:
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. |
https://github.com/kubernetes-sigs/kpng/blob/master/hack/test_skip_list.sh#L138
Seems to highlight LOTS of NFT errors on ipv6...
Are they all related. ?
The text was updated successfully, but these errors were encountered: