------- Original Message ------- On Tuesday, March 22nd, 2022 at 8:22 PM, Attila Pinter <adathor@protonmail.com> wrote:
------- Original Message -------
On Tuesday, March 22nd, 2022 at 7:22 PM, rbrown rbrown@suse.de wrote:
Hi Attila,
Do you have the logs from your kubeadm upgrade or your kubeadm runs of
your fresh install?
I'm confused how you can be hitting this issue when openQA does not seem
to be..
https://openqa.opensuse.org/tests/2256317#step/kubeadm/23
Regards,
Richard
Hi Richard,
Yea, it looks like a strange one, but I noticed that someone on the Kubic Matrix channel also ran into this issue. Kubeadm logs in journalctl[1] and the logs from /var/log/containers[2] is available, unfortunately only from the new cluster (1 Control Plane, 1 worker). Let me know if I can provide something else or try something on the systems.
1: https://paste.opensuse.org/83126572
2: https://drive.google.com/file/d/1PBajdUtKxpXZAygnfr3UE2MTLN51b4f3/view?usp=s...
--
Br,
A.
Reinstalled my test cluster yesterday that fixed most of the issues, but a t-u update broke things again. Disabled the t-u timer for now. So it looks like that pods are not getting an address, super weird. ``` kube-system kured-vfzmr 0/1 CrashLoopBackOff 3 (18s ago) 35s <none> dev-k8s-master-1 <none> <none> ``` I also broke my small test cluster so reinstalling that one now. This one is up to date so can play and test things on it. -- Br, A.