| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
This would work, but only for the first boot, and will probably fail on updates and switches as these entries won't be copied to the staged directory.
Sorry, something went wrong.
Sad face. That makes this pretty useless as installing to a populated ESP works without issue, only bootc status and bootc update are broken. Would the caller of list_type1_entries have to filter out these entries before calling get_verity on them? |
Sorry, something went wrong.
yes, and these need special treatment for updates/switches. Also, we need to make sure these appear last in the boot entries list etc etc. There are a few more cases that need to be handled |
Sorry, something went wrong.
|
I've been looking at this last- and previous weekend and attempting to have the caller filter these entries out would require a lot of changes as the original filename isn't included in the return value of list_type1_entries. Creating unique filenames for entries using the same efi argument would be possible (but quite annoying) by also putting the title and/or options in the filename, so instead in create_staged_bls_entries copies any non-managed BLS entry to the staging directory. |
Sorry, something went wrong.
There was a problem hiding this comment.
State resilience test seems to be failing with
content: Error: x Assertion failed.
content: ,-[/var/tmp/tmt/bootc-tmt-mldew2as-tmt-plans-integration-plan-45-composefs-corruped-state-resilience/tmt/plans/integration/plan-45-composefs-corruped-state-resilience/discover/default-0/tests/tmt/tests/booted/test-composefs-corruped-state-resilience.nu:51:12]
content: 50 |
content: 51 | ,-> assert (
content: 52 | | journalctl F_MESSAGE_ID=d264f924dadb4c31bff0412107d391fb
content: 53 | | | str contains $"No origin file for deployment bad-verity"
content: 54 | |-> )
content: : `---- It is not true.
content: 55 |
content: `----
This is because we log a journal message when we encounter an entry that bootc doesn't own (doesn't start with our prefix). I think it's better now to change this error message as we are handling these entries
Sorry, something went wrong.
|
Nooo... I'm not really sure how these entries end up here as list_bootloader_entries receives them from the changed get_sorted_type1_boot_entries_helper. Or is this test for grub with a user.cfg file? |
Sorry, something went wrong.
| staged_entries.atomic_write(filename, new_entry.to_string().as_bytes())?; | ||
| } | ||
|
|
||
| let original_entries = boot_dir.open_dir(TYPE1_ENT_PATH)?; |
There was a problem hiding this comment.
This is fine, but this is only for backwards compatibility stuff. The actual code for writing the staged entries would be somewhere in crates/lib/src/bootc_composefs/boot.rs
Sorry, something went wrong.
|
CI errors are unrelated to this PR |
Sorry, something went wrong.
|
I'm not entirely happy with what I had to do to create a BootSetupType Upgrade in test_write_systemd_uki_config, but adding it to a (new) tmt test was a bit too intimidating |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Fixes #2228
The cases that the tests in the last commit check cannot occur anymore because of the changes in get_sorted_type1_boot_entries_helper. If they're unneeded, I can drop the commit.