-
Notifications
You must be signed in to change notification settings - Fork 288
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
Node VMs (1.9.6) "NotReady" after restart: update-grub corrupts /boot/grub/grub.cfg #412
Comments
Below is the boot log from serial console after having modified the In the end it seems the eth0 network interface is not found, which means the VM is unreachable, services don't start, etc.
Full log:
It stays stuck there for a long time and then starts again:
|
I tried upgrading the kernel:
Then it re-boots OK. Not sure why :-| Will try the steps on another node. |
I just tried again with a new AKS cluster in eastus and did not see the problem anymore. I think the issue might have been due to some changes in the underlying Ubuntu image. |
I also recreated an AKS cluster yesterday, and try to reproduce it. In fact it turned out again that esp. running update-grub isn't stable. First lines of grub.cfg on Node-0 (getting stuck):
vs. first lines of grub.cfg on Node-1 (getting Ready):
However, both files seem to be malformed (I read them with |
When I tried the initial described commands yesterday (that was with kubernetes 1.9.9) they worked for me. Btw. here's a more safe way to add "swapaccount=1":
|
Closing as stale. |
When deploying a 3 node (kubernetes 1.9.6) cluster with "az aks create ..." we need to modify and reboot every kubernetes node for enabling "swapaccount=1".
When doing that every single node will enter "NotReady" state - my suspision is that VMs got stuck at GRUB bootloader not booting.
I'm able to work around that, with just modifying /boot/grub/grub.cfg and restarting the VMs. So it's likely there's an issue within "update-grub".
Here's what we do to modify and restart each VM (worked ~4 weeks before):
Here's the resulting /boot/grub/grub.cfg:
The text was updated successfully, but these errors were encountered: