Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Creating an IPv6 cluster multinode hangs when Joining worker nodes #87174

Closed
ricardo-rod opened this issue Jan 14, 2020 · 4 comments
Closed

Creating an IPv6 cluster multinode hangs when Joining worker nodes #87174

ricardo-rod opened this issue Jan 14, 2020 · 4 comments

Comments

@ricardo-rod
Copy link

@ricardo-rod ricardo-rod commented Jan 14, 2020

What happened:
When I am trying to run a multinode or multinode HA cluster with IPv6 it just hangs in there for so many minutes that I have stopped counting,

What you expected to happen:
The nodes should join the cluster after less than 2 minutes and I have wait 45 minutes and nothing.

How to reproduce it (as minimally and precisely as possible):
cat <./kind_multinode_ipv6.yaml

kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
nodes:

  • role: control-plane
  • role: worker
  • role: worker
    networking:
    ipFamily: ipv6
    EOF

time kind create cluster --name multinode_ipv6 --config kind_multinode_ipv6.yaml

Anything else we need to know?:
I tried global IPv6 routing space and IPv6 unique local address and i've got the same results.

Environment:

  • Kubernetes version (use kubectl version):

Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.0", GitCommit:"70132b0f130acc0bed193d9ba59dd186f0e634cf", GitTreeState:"clean", BuildDate:"2019-12-07T21:20:10Z", GoVersion:"go1.13.4", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.0", GitCommit:"70132b0f130acc0bed193d9ba59dd186f0e634cf", GitTreeState:"clean", BuildDate:"2020-01-14T00:09:19Z", GoVersion:"go1.13.4", Compiler:"gc", Platform:"linux/amd64"}

  • Cloud provider or hardware configuration:
    Laptop: 64gb ram and i7-7700HQ CPU @ 2.80GHz

  • OS (e.g: cat /etc/os-release):
    SUPPORT_URL="https://fedoraproject.org/wiki/Communicating_and_getting_help"
    BUG_REPORT_URL="https://bugzilla.redhat.com/"
    REDHAT_BUGZILLA_PRODUCT="Fedora"
    REDHAT_BUGZILLA_PRODUCT_VERSION=31
    REDHAT_SUPPORT_PRODUCT="Fedora"
    REDHAT_SUPPORT_PRODUCT_VERSION=31
    PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy"
    VARIANT="Workstation Edition"
    VARIANT_ID=workstation

  • Kernel (e.g. uname -a):
    Linux ryzen 5.4.7-200.fc31.x86_64 #1 SMP Tue Dec 31 22:25:12 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  • Install tools:

  • Network plugin and version (if this is a network-related bug):

  • Others:

@athenabot

This comment has been minimized.

Copy link

@athenabot athenabot commented Jan 14, 2020

/sig network

These SIGs are my best guesses for this issue. Please comment /remove-sig <name> if I am incorrect about one.

🤖 I am a bot run by vllry. 👩‍🔬

@k8s-ci-robot k8s-ci-robot added sig/network and removed needs-sig labels Jan 14, 2020
@athenabot

This comment has been minimized.

Copy link

@athenabot athenabot commented Jan 14, 2020

/triage unresolved

Comment /remove-triage unresolved when the issue is assessed and confirmed.

🤖 I am a bot run by vllry. 👩‍🔬

@aojea

This comment has been minimized.

Copy link
Member

@aojea aojea commented Jan 14, 2020

@ricardo-rod do you mind closing this bug and open a new one in the KIND project https://github.com/kubernetes-sigs/kind ? 😄

I'll follow up there.

Also, check that you are using the right config
https://kind.sigs.k8s.io/docs/user/quick-start/#ipv6-clusters

@ricardo-rod

This comment has been minimized.

Copy link
Author

@ricardo-rod ricardo-rod commented Jan 15, 2020

Sorry my bad, I will be closing this :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.