-
Notifications
You must be signed in to change notification settings - Fork 32
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
flatcar-install fails when using path disk devices with multiple copies #1506
flatcar-install fails when using path disk devices with multiple copies #1506
Comments
Hello @jqueuniet, The flatcar install script can be found here https://github.com/flatcar/init/blob/flatcar-master/bin/flatcar-install: According to the man page of Can you please run this command on your server to confirm?
Thank you. |
Made a possible fix here, let me know if it fixes the issue: https://github.com/ader1990/init/blob/fix-multiple-devices-same-label-install/bin/flatcar-install |
It looks like it does solve my issue. The only side-effect I can see is that it returns the canonical device path ( root@localhost ~ # blkid -t "LABEL=OEM" -o device /dev/disk/by-path/pci-0000\:44\:00.0-ata-1*
/dev/disk/by-path/pci-0000:44:00.0-ata-1-part6
/dev/disk/by-path/pci-0000:44:00.0-ata-1.0-part6
root@localhost ~ # blkid -l -t "LABEL=OEM" -o device /dev/disk/by-path/pci-0000\:44\:00.0-ata-1
/dev/sdb6 By the way, here are the SATA controller details, in case anyone needs them:
|
Great to hear that it solves your issue. I will draft a PR to get some comments and see how I can improve. For the moment, can you use the fork code or you need the patch asap in the main? Thanks. |
I'm not in a hurry, using the device with the longest name to only get a single match is a viable workaround for me until this fix hits the next release. I mostly wanted to report this as the error is a bit cryptic, the default mount behavior with no filesystem hint ends up detecting this broken path as an NFS share, which results in spending a lot of time trying to mount the OEM partition as such before hitting timeout and returning with a misleading error. Anyway, thanks a lot for the quick solution. |
Description
flatcar-install fails when using path disk devices with multiple copies
ie:
Impact
Install script fails to mount the OEM partition to write the ignition file
Expected behavior
Install script completes successfully.
Additional information
The following command does work:
It seems the root cause is the way the OEM partition is located using
blkid
to write the Ignition file.This command returns multiple values in our case but handled like a single path, which consequently fails.
The text was updated successfully, but these errors were encountered: