-
Notifications
You must be signed in to change notification settings - Fork 49
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
Bump toolchain/luet to 0.16.6 #260
Conversation
cOS-cibot
commented
Jun 11, 2021
01d6030
to
1e4fc5b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Waiting for CI tests
14ef711
to
223c17b
Compare
I've opened an issue for #277 . The timeouts issues looks like a recurring problem which seems genuine to me. |
6086a35
to
8c73fb0
Compare
I'm having a look closer, it looks like it fails 100% of times during upgrade tests |
Yes something odd is happening. See that #272 also fails on upgrade tests but with a different error... something related to xattrs not being copied by rsync... @_@ I was looking at upgrade tests now too, and of course they pass locally 😢 |
Ok, something seems definetly not ok, this is what I get trying manually:
|
To note, the release version after booting it's fine. It's just that I cannot anymore login via ssh with the vagrant user. I can login to the terminal with root/cos just fine.. |
Is the IP the same one after reboot? probably this is a known_hosts issue, I am seeing it in libvirt. If so probably persisting some of the volatile wicked config files might do the trick. |
yup, I always get I've also checked all permissions and try to restore those manually, nothing wrong there :/ |
Definetly it's something happening after a reboot. If I switch back to the fallback partition which is the same one where I was booting at the beginning, I can't login from there as well |
Another weird thing I'm noticing. Even if |
SSH finger prints are recreated on each boot, see |
oh right! I just assumed we persisted all of those. Going to try that 👍 |
What I can't understand it why is this popping up right now, its been like that since the very beginning 🤷♂️ |
Yep indeed.. It could have also been some update on the GHA runners, it looks like things degraded significantly since last outage :/ |
I just saw another failure that might cause this sort of issues, one of my local tests execution failed to login after reboot. I logged into the machine directly on tty0 from VirtualBox and I saw dbus service failed to start because of hitting restart limit, complaining of too many repeated restarts in short time, this causes a wicked service failure too, so it did not get any IP... |
I've tried to move back to the old mechanism we used to unpack images: mudler/luet@8780e4f - but testing locally yields the same results |
Created #286 for the persisting the ssh generated keys on first-boot |
I'll try to see if the issue is still there with |
7b56b42
to
aa15927
Compare
Alright, looks indeed an issue with the usage of unprivileged installs introduced in mudler/luet@796967c. A switch might do it for the time being ( see #287 ) |
Signed-off-by: David Cassany <dcassany@suse.com>
Signed-off-by: David Cassany <dcassany@suse.com>
Signed-off-by: David Cassany <dcassany@suse.com>
…ancher#260) This commit ensures repository architecture is properly propageted from `--repo` flag down to luet repository configuration. In addition a repository without any architecture is set to the current target architecture in v1.Config. Finally a `Sanitize()` method is added to `v1.BuildConfig` type. Signed-off-by: David Cassany <dcassany@suse.com>