k3s / k8s consistently not starting properly
Activity
Waqar Ahmed July 30, 2021 at 12:57 PM
in the duplicate ticket changes were introduced to make sure that we properly wait for the interfaces to be ready before configuring routes. Issue in your case is that when the route for vlan interface is being added - the interface is not ready and system fails at that point. So kubernetes not starting is a side effect of that issue.
Please let us know if this persists in 21.08, thanks!
cyrus104 July 30, 2021 at 12:51 AM
Ah, I would like to try to stay on the stable train. It looks like 21.08 BETA is only a "couple" weeks away based on the schedule not baring any major issues.
Waqar Ahmed July 29, 2021 at 2:10 PM
That issue has been closed and i believe already tackled in nightlies. Can you please test latest nightly available ? Also just to be clear, we can't go from nightlies to stable train like 21.08 BETA from the UI at least - so if you do make the transition, please keep that in mind. Kindly let me know in both cases as if you're not willing to jump to nightlies, we can close this and see if it's still a problem in 21.08 BETA. Thanks
cyrus104 July 29, 2021 at 1:55 PM
Sure did,
Waqar Ahmed July 29, 2021 at 1:27 PM
can you please confirm the ticket number again which we are waiting for ? I think you missed a digit
Details
Details
Assignee
Triage TeamReporter
cyrus104Labels
Impact
Fix versions
Affects versions
Priority
LowMore fields
Time tracking
More fields
Time trackingKatalon Platform
Linked Test Cases, Katalon Defect Results, Katalon Studio Test Results
Katalon Platform
I perviously had a couple of tickets open dealing with Plex but really k3s/k8s not starting properly after a complete power failure... my ups fails and it doesn't support NUT or anything to properly power down (I'm working on a fix).
Going through the journal output, I got this error: "container runtime network not ready" for the k3s service. It's trying to find a file.
I was able to fix this by changing the Route v4 Interface in the menu below. I had to change it then change it back to the correct setting. But for some reason the Kubernetes service keeps trying to start before the vlan interface? Even after boot there is the same issue but if I change it away and then back, it takes about 30 seconds and then it all starts up.
I hope this can help lead to a permanent solution.
I have tested this several times, if I have a vlan set as the " Route v4 Interface", k3s/k8s will not start properly.
Thanks
Will upload a private diagnostic file.