Skip to content
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

install: print warning when system may have more than one boot/root partition #642

Closed
wants to merge 1 commit into from

Conversation

nikita-dubrovskii
Copy link
Contributor

Inspired by: coreos/fedora-coreos-tracker#976

Signed-off-by: Nikita Dubrovskii [email protected]

@bgilbert
Copy link
Contributor

If the coreos-installer run is automated (e.g. with coreos.inst.install_dev) this will present as an install failure. Is that the intention?

It's also subject to false positives and especially false negatives. If coreos-installer is being run not on the target system (for example, writing to an external disk and then moving it to a different machine, or writing to a guest VM disk from the host), it won't know what other disks will be attached to the target system. And if it's being run from one FCOS system to install to a target disk for a different system (maybe this never happens?), or on a different OS that uses the boot/root labels, the error will be incorrect.

@jlebon
Copy link
Member

jlebon commented Sep 29, 2021

Yeah, we shouldn't make this a hard error, but as a warning or maybe even a note it'd be helpful. In interactive installs, it'll be noticed and acted upon in time. In automated installs, it'll be missed, but then we would catch it at reboot time if we go that way in coreos/fedora-coreos-tracker#976. So this is just about opportunistically trying to save users grief when possible (because it saves them another install iteration).

@nikita-dubrovskii nikita-dubrovskii changed the title install: ensure system has only one boot/root partition install: print warning when system may have more than one boot/root partition Sep 30, 2021
@nikita-dubrovskii
Copy link
Contributor Author

If the coreos-installer run is automated (e.g. with coreos.inst.install_dev) this will present as an install failure. Is that the intention?

it was.

If coreos-installer is being run not on the target system..

yep, missed those cases.

Yeah, we shouldn't make this a hard error, but as a warning

done

@nikita-dubrovskii nikita-dubrovskii deleted the single_boot branch October 7, 2021 08:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants