-
Notifications
You must be signed in to change notification settings - Fork 96
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
k3s network (coredns) problems with v2.2.1-k3sv1.26.4-k3s1 #1525
Comments
I tried a fresh install:
and it works as expected.
I can try an upgrade. @Ognian which version did you upgrade from? |
|
@jimmykarily
is trying to connect to 192.168.6.64 BUT |
@jimmykarily Ups there is no |
The IP address change may be related to this: #1381 which got fixed and then got fixed again. If that's the problem then either you wait until today's release is out (which has the fix) or you try to change the IP address manually to what it was (I see some options here but I'm not sure how to do that on a read-only OS: k3s-io/k3s#5787). Also, the fix is based on us storing the machine-id so that we can restore it. I'm not sure if upgrading to this version will find the old machine-id stored. @Itxaka since you implemented the fix, do you think it's going to work? Probably the broken versions should be skipped (so that the IP address doesn't change with the reboots). Another thing, is it needed that all upgrades are applied? Can't @Ognian just upgrade from 1.6 to the latest in one step? |
Also, if this is indeed the issue, we should add it to the release notes (e.g. which versions to skip to avoid this problem). I assume, for those who used static IP addresses, it's not a problem. |
It should be possible I think. The original machine-id should still be under Then once upgraded to the fixed version, it should auto pick teh exiting machine-id and save it under /etc/machine-id which should give you the fixed IP back...I think. But after upgrade, for sure it wont change again. If a fixed IP is required it also should be possible to skip dhcp and set it manually via https://kairos.io/docs/advanced/networking/#static-ip meanwhile |
this did not work. I had to do a reset... |
I did some additional test today:
any ideas? |
@Ognian these logs don't seem to be the cause of the problem. There just say that edgevpn is working fine. When you say "there is no network" I assume you mean you can't SSH. This could be cause by various problems not related to networking. E.g. even a syntax error in the cloud config could break SSH (because user accounts won't be created). Eventually you SSHed to the machine so I assume it worked. Regarding the original problem, does k3s now start? Does it use the correct IP address? If you can also attach the output of |
@jimmykarily sorry for not being precise enough. When I say "there is no network" I mean the rpi does not have an ip address (on finishing boot you display the kairos in ascii art and below So what I wanted to say is that only after 3 reboots I was able to get an IP and than ssh into the machine was without any problem. Here are the logs:
|
@Ognian this seems to have gotten the
|
sudo journalctl -u k3s-agent:
the actual error when you scroll right is
I would say that the state partition is no more expanded after first boot (#1448) |
I could be. I can't tell which partition is which in kairos from the output above (This command will make it clearer I think the only partition that would automatically get expanded would be You probably hit the bug you linked but I'm not 100% sure that this is the only problem you are facing. That bug has a fix which I'm trying to test here: https://github.com/kairos-io/kairos/pull/1497/files but I'm facing CI issues since last week and haven't been able to verify it's ok to merge. Stay tuned. |
|
Yes, |
Kairos version:
NAME="openSUSE Leap"
VERSION="15.4"
ID="opensuse-leap"
ID_LIKE="suse opensuse"
VERSION_ID="15.4"
PRETTY_NAME="openSUSE Leap 15.4"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:leap:15.4"
BUG_REPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org/"
DOCUMENTATION_URL="https://en.opensuse.org/Portal:Leap"
LOGO="distributor-logo-Leap"
KAIROS_NAME="kairos-opensuse-leap"
KAIROS_VERSION="v2.2.1-k3sv1.26.4+k3s1"
KAIROS_ID="kairos"
KAIROS_ID_LIKE="kairos-opensuse-leap"
KAIROS_VERSION_ID="v2.2.1-k3sv1.26.4+k3s1"
KAIROS_PRETTY_NAME="kairos-opensuse-leap v2.2.1-k3sv1.26.4+k3s1"
KAIROS_BUG_REPORT_URL="https://github.com/kairos-io/kairos/issues/new/choose"
KAIROS_HOME_URL="https://github.com/kairos-io/provider-kairos"
KAIROS_IMAGE_REPO="quay.io/kairos/kairos-opensuse-leap"
KAIROS_IMAGE_LABEL="latest"
KAIROS_GITHUB_REPO="kairos-io/provider-kairos"
KAIROS_VARIANT="core"
KAIROS_FLAVOR="opensuse-leap"
CPU architecture, OS, and Version:
Linux lp3dnode 5.14.21-150400.24.63-default #1 SMP PREEMPT_DYNAMIC Tue May 2 15:49:04 UTC 2023 (fd0cc4f) x86_64 x86_64 x86_64 GNU/Linux
Describe the bug
coredns can't start:
To Reproduce
upgraded from a previous working version
maybe on a new install it will also reproduce...
Expected behavior
Logs
Additional context
Maybe related to this:
k3s-io/k3s#7013
but this https://docs.k3s.io/advanced#old-iptables-versions
did not help or I did not manage to apply....
The text was updated successfully, but these errors were encountered: