-
Notifications
You must be signed in to change notification settings - Fork 97
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
🐛 nohang service fails on Ubuntu 23.10 #2195
Comments
Kevin tested this with a new cluster, and it spins up fine. I don't understand how we use nohang exactly, so not sure if it's an issue. We will only find out with a loaded cluster, or if nohang is used for something specific that needs to be tested |
upstream have a fix for this hakavlad/nohang#136, hope new release of nohang fix the issue. |
Today, we install nohang from ppa, which might not up to date. I think would consider to install it from source, we then have the fix. |
nohang apt repo is not actively maintained, install it from source instead. try to fix kairos-io#2195 Signed-off-by: Liyi Meng <[email protected]>
nohang apt repo is not actively maintained, install it from source instead. try to fix kairos-io#2195 Signed-off-by: Liyi Meng <[email protected]>
* Install nohang from source for ubuntu nohang apt repo is not actively maintained, install it from source instead. try to fix #2195 Signed-off-by: Liyi Meng <[email protected]> * Refactoring 1. We don't need zfs on UKI images 2. gnupg is not needed in common 3. Renaming of targets to legacy and current, to re-use between 22+ versions Signed-off-by: Mauro Morales <[email protected]> * Re-generate Dockerfile.kairos-ubuntu Signed-off-by: Mauro Morales <[email protected]> * Lint Signed-off-by: Mauro Morales <[email protected]> --------- Signed-off-by: Liyi Meng <[email protected]> Signed-off-by: Mauro Morales <[email protected]> Co-authored-by: Mauro Morales <[email protected]>
tried with the alpha but I found this issue already on 2.5.0
nohang status
Seems to be related to hakavlad/nohang#135 so we might need to bump the version once it is released. Or maybe we can even provide it as part of the framework image like suggested here #1609 (comment)
The text was updated successfully, but these errors were encountered: