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

Vagrant with Rockylinux8: etcd cannot start: No route to host #10251

Closed
nltimv opened this issue Jun 24, 2023 · 0 comments · Fixed by #10252
Closed

Vagrant with Rockylinux8: etcd cannot start: No route to host #10251

nltimv opened this issue Jun 24, 2023 · 0 comments · Fixed by #10252
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@nltimv
Copy link
Contributor

nltimv commented Jun 24, 2023

Environment:

  • Cloud provider or hardware configuration:
    Desktop PC (AMD Ryzen 9 7900X, 32GB Memory)

  • OS (printf "$(uname -srm)\n$(cat /etc/os-release)\n"):

Linux 6.3.9-arch1-1 x86_64
NAME="Arch Linux"
PRETTY_NAME="Arch Linux"
ID=arch
BUILD_ID=rolling
ANSI_COLOR="38;2;23;147;209"
HOME_URL="https://archlinux.org/"
DOCUMENTATION_URL="https://wiki.archlinux.org/"
SUPPORT_URL="https://bbs.archlinux.org/"
BUG_REPORT_URL="https://bugs.archlinux.org/"
PRIVACY_POLICY_URL="https://terms.archlinux.org/docs/privacy-policy/"
LOGO=archlinux-logo
  • Version of Ansible (ansible --version):
ansible [core 2.12.10]
  config file = /home/nltimv/workspace/kubespray/ansible.cfg
  configured module search path = ['/home/nltimv/workspace/kubespray/library']
  ansible python module location = /home/nltimv/workspace/kubespray/venv/lib/python3.11/site-packages/ansible
  ansible collection location = /home/nltimv/.ansible/collections:/usr/share/ansible/collections
  executable location = /home/nltimv/workspace/kubespray/venv/bin/ansible
  python version = 3.11.3 (main, Jun  5 2023, 09:32:32) [GCC 13.1.1 20230429]
  jinja version = 3.1.2
  libyaml = True
  • Version of Python (python --version):
    Python 3.11.3

Kubespray version (commit) (git rev-parse --short HEAD):
eb31653d6

Network plugin used:
flannel

Full inventory with variables (ansible -i inventory/sample/inventory.ini all -m debug -a "var=hostvars[inventory_hostname]"):

n/a

Command used to invoke ansible:
sudo vagrant up --provider=libvirt --provision

Output of ansible run:

https://gist.github.com/nltimv/5351c02c4a5a3c2e0bd93ab9365d7f18

TASK [etcd : Configure | Ensure etcd is running] *******************************
fatal: [kub-2]: FAILED! => {"changed": false, "msg": "Unable to start service etcd: Job for etcd.service failed because a timeout was exceeded.\nSee \"systemctl status etcd.service\" and \"journalctl -xe\" for details.\n"}
fatal: [kub-3]: FAILED! => {"changed": false, "msg": "Unable to start service etcd: Job for etcd.service failed because a timeout was exceeded.\nSee \"systemctl status etcd.service\" and \"journalctl -xe\" for details.\n"}
fatal: [kub-1]: FAILED! => {"changed": false, "msg": "Unable to start service etcd: Job for etcd.service failed because a timeout was exceeded.\nSee \"systemctl status etcd.service\" and \"journalctl -xe\" for details.\n"}
zaterdag 24 juni 2023  16:21:44 +0200 (0:01:30.519)       0:05:09.961 ********* 
zaterdag 24 juni 2023  16:21:44 +0200 (0:00:00.000)       0:05:09.961 ********* 

Anything else do we need to know:

Output of sudo journalctl -xe | tail -n 200 | grep etcd in one of the VM's:
https://gist.github.com/nltimv/4817e85e7d152f1e88b8d6052d04ecd1
Note the connection errors here:

{"level":"warn","ts":"2023-06-24T14:25:05.586Z","caller":"rafthttp/probing_status.go:68","msg":"prober detected unhealthy status","round-tripper-name":"ROUND_TRIPPER_SNAPSHOT","remote-peer-id":"741516e05330a44d","rtt":"0s","error":"dial tcp 10.0.20.102:2380: connect: no route to host"}

Stopping firewalld.service does the trick for me. This is already done automatically for other Red Hat based distros in the Vagrantfile, but not for Rocky Linux 8. I will submit a PR adding Rocky Linux to that list shortly

@nltimv nltimv added the kind/bug Categorizes issue or PR as related to a bug. label Jun 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant