-
Notifications
You must be signed in to change notification settings - Fork 93
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
coreos-installer not finishing install properly on single core/thread vm's #575
Comments
changed coreos-installer/src/blockdev.rs Line 984 in 18f3cb1
to |
tested using a live fedora core 34 worktion ISO and it was able to install onto |
coreos-installer does not build on debian:buster (stable) using debian:testing as the builder container and debian:stable as the resultant build container (with matching udev as host) works.
|
adding
|
Thanks for tracking this down. In summary, it looks like there's a mismatch between the newer udevadm in the coreos-installer container and an older version of udevd on the host. And the problem doesn't happen in all cases, only on a (these days) relatively rare hardware configuration. I'm not sure there's a lot we can do about this. For now, my best suggestion for anyone experiencing this issue is to use |
I went and searched the |
Sorry. Swiping through the issue I accidentally closed |
I think the best way to handle this type of stuff is to use e.g. |
Bug
coreos-installer not working most of the time on single core/thread VMs.
I have tried it on the same vm with one thread and got it to finish successfully a few times out of hundred by re-running the below docker command and doing disk IO related commands while it was reading the image in another connection to it.
EG
find /
du
while sleep .1; echo w | fdisk /dev/sda; done
or seemingly luck.I initially thought it was a lack of memory problem as a 4GB vm on the same provider (hetzner) would work with the method below, but that VM had 2 cpus. So I tried a 2cpu 2GB and that worked.
I then tried the same method on 1 thread 2GB VM on vultr running an old CoreOS (OG) version and had the same udevadm settle problem.
Host Operating System Version
Debian 10 buster live on Hetzner with docker 18.01
also CoreOS (OG) stable (1185.5.0) ISO on Vultr
Target Operating System Version
CoreOS Stable v 34.20210626.3.1
coreos-installer Version
quay.io/coreos-installer:release
quay.io/coreos-installer:latest
quay.io/coreos-installer:0.9.2-alpha.0
Expected Behavior
Installation Successful
Actual Behavior
Reproduction Steps
see docker command above.
The text was updated successfully, but these errors were encountered: