Closed c10l closed 3 months ago
We can't guess but it looks like the machine never left the maintenance mode, so it probably failed somewhere on the way after the machine config got applied.
You can enable serial console logs in Proxmox and capture full logs after the apply-config phase and see what went wrong.
Thanks @smira . I've captures those logs but I'm none the wiser.
The logs above include the very first boot and the apply-config
operation all the way until it reboots.
Only thing that stood out above was the inability to resolve time.cloudflare.com
via 1.1.1.1
or 8.8.8.8
. I don't allow machines in this network to reach public DNS servers, so I configured it to use the internal DNS server and rebooted.
At this point, it resolved the NTP server fine and synced the system time. The Kubernetes services still fail to come up.
Your IP 10.100.0.100
might overlap with default pod/service subnets (https://www.talos.dev/v1.7/introduction/troubleshooting/#conflict-on-kubernetes-and-host-subnets).
Ah, thank you! That was it. So basically, RTFM! 😅 I changed my CIDR to 100.200.0.0/16
and it all fell into place.
Bug Report
Description
I'm trying to install Talos on Proxmox, following this guide: https://www.talos.dev/v1.7/talos-guides/install/virtualized-platforms/proxmox/
I created the master VM, exported its IP as
CONTROL_PLANE_IP
.I then generated the config:
Applied config to master node:
After a little while, the machine reboots but never comes back up properly. It stays stuck on this state:
Logs
Other than what can be seen in the screenshot, I'm not sure how to capture any more logs.
Environment
talosctl version --nodes <problematic nodes>
]amd64