Install script not working correctly on the latest versions #1059
Comments
|
What OS+version are you running |
|
The install script works correctly on Beta 3572.1.0. |
|
That's a great hint, thanks. @krishjainx would you investigate this? |
|
Certainly
…On Mon, Jun 5, 2023, 11:24 AM Jeremi Piotrowski ***@***.***> wrote:
That's a great hint, thanks. @krishjainx <https://github.com/krishjainx>
would you investigate this?
—
Reply to this email directly, view it on GitHub
<#1059 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AR4RDLO7QD6CXSURGMGVNBDXJWQWPANCNFSM6AAAAAAY2TP76E>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
@jepio @DmitryMigunov FWIW, I tried reproducing the issue in a qemu vm and couldn't replicate the issue.
|
|
Hmm, on the Ubuntu live-boot it was working ^ but it doesn't successfully install Flatcar linux beta 3602.1.0 if Ubuntu is installed to the virtual disk.
This is still the case even after masking systemd-fsck@.service which was the suggested workaround according to #120 - coreos/bugs#152 (comment) . |
|
Debug output
Hangs at blockdev command for me. |
|
We created an empty VM on qemu (Proxmox 7.4-3) and booted from Beta 3602.1.0 iso. Proxmox VM config:
|
|
@DmitryMigunov Could you try |
|
Same result UPDATE: |
|
We tried to install it on bare metal and got the same problem. |
|
I faced this issue while trying to build cluster API Flatcar image using |
|
I think you are right, the issue is related to bash. We successfully installed the system using bash 5.1. But we still received messages |
That's not an actual error: it's because we're writing a fixed size disk image to a larger disk, and the disk image being written has the GPT alt header. This gets corrected later (during first-boot I think). |
|
I investigated further and it's actually this |
|
I often use alpine, GParted maybe a better choice ? #998 |
|
We have recently also the problem that the flatcar-install script is no longer executed successfully. The background is that the However, if we do a strace on the command in flatcar-install, we see a successful Our Provider updated the rescue image we are using to install flatcar. the current version is When we switch back to the old Debian 11 rescue image, the install process is working again. We have successfully tested this flatcar/init#97 pull request on both rescue images. |
|
Thanks @procinger for the feedback and for testing the proposed fix. I'm still trying to pin point the root cause: as @pothos mentioned, this script is being tested as part of Flatcar CI so we should have seen this earlier but it's not the case and I can't come yet with a simple repro. |
|
The fix is merged for the next Alpha and Beta releases |
Description
Flatcar install script couldn't finish the installation. It sticks on
udevadm settlecommand and outputting to tty:Impact
We cannot install the system
Environment and steps to reproduce
Version: Beta 3602.1.0 / Alpha 3619.0.0
Version Beta 3572.1.0 installs without errors.
Expected behavior
The system installs successfully
The text was updated successfully, but these errors were encountered: