-
Notifications
You must be signed in to change notification settings - Fork 355
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
bootupd: Use --write-uuid #5363
Conversation
I didn't test this locally (still don't have an anaconda devenv) but hopefully someone can sanity check this. |
@cgwalters Can you fix the unit tests, please? It should be a one-liner. anaconda/tests/unit_tests/pyanaconda_tests/modules/payloads/payload/test_rpm_ostree_tasks.py Line 780 in f921b0c
@VladimirSlavik is working on integrations tests. We can try them on your pull request tomorrow. Btw. we are able to generate a boot.iso from your pull request if you want to play with it. |
This is an even newer behavior that takes over handling of the "UUID stamp files", which we want in general instead of using the static labels. Note `--write-uuid` implies `--with-static-configs`. This should fix this use case: ``` clearpart --all --initlabel --disklabel=gpt reqpart --add-boot part / --grow --fstype xfs ``` Whereas right now we require: ``` clearpart --all --initlabel --disklabel=gpt reqpart part /boot --size=1000 --fstype=ext4 --label=boot part / --grow --fstype xfs ``` Specifically the `--label=boot`.
/kickstart-test --testtype smoke |
SGTM yes! |
Turns out, the tests are not exactly easy to adapt for ostree and reboot at once :( |
Use a fixed kickstart to cut corners, this needs a PoC as soon as possible. We need manual partitioning because we need to set the boot label on the `/boot` partition. It is possible that this won't be necessary in the future: rhinstaller/anaconda#5363 We'll remove the kickstart literal once the PR is merged and the options used are merged into the kickstart stage.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. Thank you!
Tested manually. It seems to work, so I am merging this pull request. There should be a new release on Tuesday. |
Thanks! I just wanted to briefly explain here for the record; it may be obvious to some but still: the reason we need a distinction between the two In the CoreOS case there's logic that runs in the initramfs at boot time to generate the UUIDs. So the logic today in coreos-assembler (that is now being replicated in osbuild) will use In this we are assuming Anaconda is not used to make "generic" images. That said it doesn't really matter too much...I honestly want to try really hard to get away from the "coreos-installer" type "dd raw disk image" for bare metal installs because there are just so many traps/problems (e.g. 4kn disks...) |
Use a fixed kickstart to cut corners, this needs a PoC as soon as possible. We need manual partitioning because we need to set the boot label on the `/boot` partition. It is possible that this won't be necessary in the future: rhinstaller/anaconda#5363 We'll remove the kickstart literal once the PR is merged and the options used are merged into the kickstart stage.
Use a fixed kickstart to cut corners, this needs a PoC as soon as possible. We need manual partitioning because we need to set the boot label on the `/boot` partition. It is possible that this won't be necessary in the future: rhinstaller/anaconda#5363 We'll remove the kickstart literal once the PR is merged and the options used are merged into the kickstart stage.
Use a fixed kickstart to cut corners, this needs a PoC as soon as possible. We need manual partitioning because we need to set the boot label on the `/boot` partition. It is possible that this won't be necessary in the future: rhinstaller/anaconda#5363 We'll remove the kickstart literal once the PR is merged and the options used are merged into the kickstart stage.
Use a fixed kickstart to cut corners, this needs a PoC as soon as possible. We need manual partitioning because we need to set the boot label on the `/boot` partition. It is possible that this won't be necessary in the future: rhinstaller/anaconda#5363 We'll remove the kickstart literal once the PR is merged and the options used are merged into the kickstart stage.
Use a fixed kickstart to cut corners, this needs a PoC as soon as possible. We need manual partitioning because we need to set the boot label on the `/boot` partition. It is possible that this won't be necessary in the future: rhinstaller/anaconda#5363 We'll remove the kickstart literal once the PR is merged and the options used are merged into the kickstart stage.
Use a fixed kickstart to cut corners, this needs a PoC as soon as possible. We need manual partitioning because we need to set the boot label on the `/boot` partition. It is possible that this won't be necessary in the future: rhinstaller/anaconda#5363 We'll remove the kickstart literal once the PR is merged and the options used are merged into the kickstart stage.
Use a fixed kickstart to cut corners, this needs a PoC as soon as possible. We need manual partitioning because we need to set the boot label on the `/boot` partition. It is possible that this won't be necessary in the future: rhinstaller/anaconda#5363 We'll remove the kickstart literal once the PR is merged and the options used are merged into the kickstart stage.
Use a fixed kickstart to cut corners, this needs a PoC as soon as possible. We need manual partitioning because we need to set the boot label on the `/boot` partition. It is possible that this won't be necessary in the future: rhinstaller/anaconda#5363 We'll remove the kickstart literal once the PR is merged and the options used are merged into the kickstart stage.
Use a fixed kickstart to cut corners, this needs a PoC as soon as possible. We need manual partitioning because we need to set the boot label on the `/boot` partition. It is possible that this won't be necessary in the future: rhinstaller/anaconda#5363 We'll remove the kickstart literal once the PR is merged and the options used are merged into the kickstart stage.
Use a fixed kickstart to cut corners, this needs a PoC as soon as possible. We need manual partitioning because we need to set the boot label on the `/boot` partition. It is possible that this won't be necessary in the future: rhinstaller/anaconda#5363 We'll remove the kickstart literal once the PR is merged and the options used are merged into the kickstart stage.
Use a fixed kickstart to cut corners, this needs a PoC as soon as possible. We need manual partitioning because we need to set the boot label on the `/boot` partition. It is possible that this won't be necessary in the future: rhinstaller/anaconda#5363 We'll remove the kickstart literal once the PR is merged and the options used are merged into the kickstart stage.
Use a fixed kickstart to cut corners, this needs a PoC as soon as possible. We need manual partitioning because we need to set the boot label on the `/boot` partition. It is possible that this won't be necessary in the future: rhinstaller/anaconda#5363 We'll remove the kickstart literal once the PR is merged and the options used are merged into the kickstart stage.
Use a fixed kickstart to cut corners, this needs a PoC as soon as possible. We need manual partitioning because we need to set the boot label on the `/boot` partition. It is possible that this won't be necessary in the future: rhinstaller/anaconda#5363 We'll remove the kickstart literal once the PR is merged and the options used are merged into the kickstart stage.
Use a fixed kickstart to cut corners, this needs a PoC as soon as possible. We need manual partitioning because we need to set the boot label on the `/boot` partition. It is possible that this won't be necessary in the future: rhinstaller/anaconda#5363 We'll remove the kickstart literal once the PR is merged and the options used are merged into the kickstart stage.
Use a fixed kickstart to cut corners, this needs a PoC as soon as possible. We need manual partitioning because we need to set the boot label on the `/boot` partition. It is possible that this won't be necessary in the future: rhinstaller/anaconda#5363 We'll remove the kickstart literal once the PR is merged and the options used are merged into the kickstart stage.
Use a fixed kickstart to cut corners, this needs a PoC as soon as possible. We need manual partitioning because we need to set the boot label on the `/boot` partition. It is possible that this won't be necessary in the future: rhinstaller/anaconda#5363 We'll remove the kickstart literal once the PR is merged and the options used are merged into the kickstart stage.
Use a fixed kickstart to cut corners, this needs a PoC as soon as possible. We need manual partitioning because we need to set the boot label on the `/boot` partition. It is possible that this won't be necessary in the future: rhinstaller/anaconda#5363 We'll remove the kickstart literal once the PR is merged and the options used are merged into the kickstart stage.
Use a fixed kickstart to cut corners, this needs a PoC as soon as possible. We need manual partitioning because we need to set the boot label on the `/boot` partition. It is possible that this won't be necessary in the future: rhinstaller/anaconda#5363 We'll remove the kickstart literal once the PR is merged and the options used are merged into the kickstart stage.
Use a fixed kickstart to cut corners, this needs a PoC as soon as possible. We need manual partitioning because we need to set the boot label on the `/boot` partition. It is possible that this won't be necessary in the future: rhinstaller/anaconda#5363 We'll remove the kickstart literal once the PR is merged and the options used are merged into the kickstart stage.
Use a fixed kickstart to cut corners, this needs a PoC as soon as possible. We need manual partitioning because we need to set the boot label on the `/boot` partition. It is possible that this won't be necessary in the future: rhinstaller/anaconda#5363 We'll remove the kickstart literal once the PR is merged and the options used are merged into the kickstart stage.
This is an even newer behavior that takes over handling of the "UUID stamp files", which we want in general instead of using the static labels.
Note
--write-uuid
implies--with-static-configs
.This should fix this use case:
Whereas right now we require:
Specifically the
--label=boot
.