Closed martwz closed 2 years ago
What OS are you using?
Can you please confirm that v1.23.6+k3s1
fails to start too?
@martinxxd I am trying to reproduce with below config on a fresh node. I am not seeing issues bringing up the cluster on Ubuntu 20.04 ipv6 only setup using v1.23.7.rc1+k3s1 as well as v1.24.1.rc1+k3s1. Any input that will be helpful to reproduce?
$ cat config.yaml
write-kubeconfig-mode: 644
token: REDACTED
cluster-cidr: 2001:cafe:42:0::/56
service-cidr: 2001:cafe:42:1::/112
disable-network-policy: true
flannel-ipv6-masq: true
disable: traefik
ubuntu@i-02f672ec94681e415:~$ kubectl get nodes
NAME STATUS ROLES AGE VERSION
i-02f672ec94681e415 Ready control-plane,master 48s v1.24.1-rc1+k3s1
ubuntu@i-02f672ec94681e415:~$ kubectl get pods -A
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system coredns-b96499967-ldjm6 1/1 Running 0 35s
kube-system local-path-provisioner-7b7dc8d6f5-zg7r5 1/1 Running 0 35s
kube-system metrics-server-668d979685-tpqkc 1/1 Running 0 35s
ubuntu@i-02f672ec94681e415:~$
@manuelbuil, @ShylajaDevadiga, thanks for getting back so promptly!
I'll gather a bit more information regarding my OS and try out v1.23.6+k3s1
. On a high-level, I'm running Rocky Linux 8
.
Do you actually have globally a routable IPv6 address on an interface, and a ipv6 default route?
yes that's an ipv6-only server, there's no (routable) ipv4 assigned.
[root@rocky ~]# cat /etc/os-release
NAME="Rocky Linux"
VERSION="8.6 (Green Obsidian)"
ID="rocky"
ID_LIKE="rhel centos fedora"
VERSION_ID="8.6"
PLATFORM_ID="platform:el8"
PRETTY_NAME="Rocky Linux 8.6 (Green Obsidian)"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:rocky:rocky:8:GA"
HOME_URL="https://rockylinux.org/"
BUG_REPORT_URL="https://bugs.rockylinux.org/"
ROCKY_SUPPORT_PRODUCT="Rocky Linux"
ROCKY_SUPPORT_PRODUCT_VERSION="8"
REDHAT_SUPPORT_PRODUCT="Rocky Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="8"
[root@rocky ~]# hostnamectl
Static hostname: rocky
Icon name: computer-desktop
Chassis: desktop
Machine ID: CENSORED
Boot ID: CENSORED
Operating System: Rocky Linux 8.6 (Green Obsidian)
CPE OS Name: cpe:/o:rocky:rocky:8:GA
Kernel: Linux 4.18.0-348.7.1.el8_5.x86_64
Architecture: x86-64
[root@rocky ~]# cat /etc/*release
Rocky Linux release 8.6 (Green Obsidian)
NAME="Rocky Linux"
VERSION="8.6 (Green Obsidian)"
ID="rocky"
ID_LIKE="rhel centos fedora"
VERSION_ID="8.6"
PLATFORM_ID="platform:el8"
PRETTY_NAME="Rocky Linux 8.6 (Green Obsidian)"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:rocky:rocky:8:GA"
HOME_URL="https://rockylinux.org/"
BUG_REPORT_URL="https://bugs.rockylinux.org/"
ROCKY_SUPPORT_PRODUCT="Rocky Linux"
ROCKY_SUPPORT_PRODUCT_VERSION="8"
REDHAT_SUPPORT_PRODUCT="Rocky Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="8"
Rocky Linux release 8.6 (Green Obsidian)
[root@rocky ~]# uname -srm
Linux 4.18.0-348.7.1.el8_5.x86_64 x86_64
[root@rocky ~]# nmcli connection show
NAME UUID TYPE DEVICE
System enp6s0 b43fa2aa-5a85-7b0a-9a20-469067dba6d6 ethernet enp6s0
tailscale0 8d9ddd75-443e-445c-b140-c4af5a80a41b tun tailscale0
cni0 8450821d-9831-4b92-a102-dc6402065dee bridge cni0
flannel-v6.1 1d0b918f-3f61-46c1-b8fb-bed18953d616 vxlan flannel-v6.1
[root@rocky ~]# nmcli device show enp6s0
GENERAL.DEVICE: enp6s0
GENERAL.TYPE: ethernet
GENERAL.HWADDR: 7C:10:C9:21:FC:C7
GENERAL.MTU: 1500
GENERAL.STATE: 100 (connected)
GENERAL.CONNECTION: System enp6s0
GENERAL.CON-PATH: /org/freedesktop/NetworkManager/ActiveConnection/1
WIRED-PROPERTIES.CARRIER: on
IP4.GATEWAY: --
IP6.ADDRESS[1]: CENSORED::2/64
IP6.ADDRESS[2]: fe80::7e10:c9ff:fe21:fcc7/64
IP6.GATEWAY: fe80::1
IP6.ROUTE[1]: dst = fe80::/64, nh = ::, mt = 100
IP6.ROUTE[2]: dst = CENSORED::/64, nh = ::, mt = 100
IP6.ROUTE[3]: dst = ::/0, nh = fe80::1, mt = 100
[root@rocky ~]# cat /etc/sysconfig/network-scripts/ifcfg-enp6s0
DEVICE=enp6s0
ONBOOT=yes
BOOTPROTO=none
DEFROUTE=yes
IPV6INIT=yes
IPV6ADDR=CENSORED::2/64
IPV6_DEFAULTGW=fe80::1
IPV6_DEFROUTE=yes
Getting the same error using v1.23.6+k3s1 (418c3fa8)
:
Does localhost
in /etc/hosts point at an ipv4, or ipv6, address?
I think that it could be a certificate issue. Are you starting the newer version of K3s on an existing setup or is a fresh installation?
oh, localhost points to an ipv4. And I'm starting the newer version of k3s on an existing setup.
[root@rocky ~]# cat /etc/hosts
127.0.0.1 localhost.localdomain localhost
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
REDACTED::2 rocky
[root@rocky ~]# ping localhost
PING localhost.localdomain (127.0.0.1) 56(84) bytes of data.
64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=1 ttl=64 time=0.030 ms
64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=2 ttl=64 time=0.041 ms
64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=3 ttl=64 time=0.022 ms
^C
--- localhost.localdomain ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 9227ms
rtt min/avg/max/mdev = 0.022/0.028/0.041/0.006 ms
The issue is related on the generated certificate, on v1.23.5
IPv6 wasn't fully supported and has some issues on the internal generated URLs with 127.0.0.1
and not ::1
, on v1.23.6
this was fixed; on your setup the certificate generated on v1.23.5
points only to 127.0.0.1
then it fails to contact the service on ::1
because it's not a valid certificate.
I have to check how to force the certificate generation.
If you remove the certificates on /var/lib/rancher/k3s/server/tls/
before updating they will be generated again from the newer version and it should be fixed.
Thanks rbrtbnfgl and brandond! Removing the certificates from /var/lib/rancher/k3s/server/tls/
fixed the issue, I'm now able to run the latest k3s using an ipv6-only setup 🎉
Environmental Info: K3s Version:
Cluster Configuration: Single-node ipv6-only server
Describe the bug: I'm running k3s using the following command:
While that works for
k3s version v1.23.5+k3s1 (313aaca5)
, it doesn't work for the latest v1.24.x and v1.23.x releases.Logs, working example using
k3s version v1.23.5+k3s1 (313aaca5)
: Full logsLogs, NOT working example using
k3s version v1.24.1-rc1+k3s1 (a5a0e8fd)
:Full logs