This message was deleted.
# general
a
This message was deleted.
p
adding worker nodes requires a lot more ports than just 443, did you check the port permission list for 6443 and 9345?
s
i have not restricted any ports in my server. even no firewall
p
what server os is it?
s
SUSE linux
p
Is flannel injecting into iptables? Sudo iptables -L
s
No it is not injecting. Here is the output from my worker ..iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination
Any issue with certificates exchange you think ?
p
I know there is a known issue w flannel and ubuntu 22.04, maybe its related? Is the new node iptables version different than the others?
s
no .. its all SUSE rancher OS installed blades on same chassis
p
Either way whats the iptables version on a good vs bad node, i just want to verify its not that
s
iptables --version iptables v1.8.7 (legacy)
cat /etc/os-release NAME="SLES" VERSION="15-SP3" VERSION_ID="15.3" PRETTY_NAME="SUSE Linux Enterprise Server 15 SP3" ID="sles" ID_LIKE="suse" ANSI_COLOR="0;32" CPE_NAME="cpe/osusesles15:sp3" DOCUMENTATION_URL="https://documentation.suse.com/"
both version same in good and bad nodes
p
I still think its some kind of lack of permissions or something with flannel, but 1000% please let me know if you find a fix, ive been fighting this same type of issue 😅
s
ok sure
found the issue . i have a token mismatch in 50-rancher.yaml file which resides under /etc/rancher/rke2/config.yaml.d "token": "klkwf9x7dvs89h7jqfrq4bg5vmt6mtdchwdcvf49xcfmtdxtwwlq5m"
🙌 1