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

Don't consider the situation where there are two IPs starting with '10'. #958

Open
huasiy opened this issue Mar 18, 2024 · 0 comments · May be fixed by #982
Open

Don't consider the situation where there are two IPs starting with '10'. #958

huasiy opened this issue Mar 18, 2024 · 0 comments · May be fixed by #982
Assignees
Labels
bug Something isn't working

Comments

@huasiy
Copy link

huasiy commented Mar 18, 2024

Describe the bug
When deploy kubernetes, create_multinode_cluster.go will obtain ip starting with 10 and pass it as a parameter for kubeadm.

masterNodeIp, iperr := utils.ExecShellCmd(`ip route | awk '{print $(NF)}' | awk '/^10\..*/'`)

However, when there is two ips starting with 10, this script fails and leave a unclean environment. I try to use scripts/github_runner/clean_cri_runner.sh and scripts/clean_fcctr.sh to clean and reinstall, I enconter error failed calling webhook "ipaddresspoolvalidationwebhook.metallb.io". To restore a clean environment, I have to execute these two cleaning scripts and reboot machine.
Therefore, there are actually two bugs: one is the inability to handle the situation where there are two IPs starting with 10, and the other is that the clean script is ineffective in this situation.
To Reproduce
Deploy in a multi-node environment, the master node has two network interfaces with IPs starting with '10'.
Machine: x86_64
OS: ubuntu20.04 LTS server
Software: stock-only
Expected behavior
Inform the user to select which network interface card to use and provide a script that can properly clean the environment.

@huasiy huasiy added the bug Something isn't working label Mar 18, 2024
@lrq619 lrq619 self-assigned this May 7, 2024
@lrq619 lrq619 linked a pull request May 9, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants