kola: Add new OEM sysext update and migration test #448
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The A/B updated OEM systemd-sysext image gets activated when both /usr partitions have updated to a version that requires a sysext image. The old OEM contents get cleaned in this migration that happens on the boot after the final update. Test this migration and update logic by starting from an old image that isn't migrated, and emulate an OEM setup that requires an OEM sysext image now. The update first happens with the inbuilt Omaha kolet server which uses the fallback logic but then flatcar-update is used for the second update to supply the OEM payload directly.
tormath1
approved these changes
Sep 6, 2023
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The A/B updated OEM systemd-sysext image gets activated when both /usr partitions have updated to a version that requires a sysext image. The old OEM contents get cleaned in this migration that happens on the boot after the final update.
Test this migration and update logic by starting from an old image that isn't migrated, and emulate an OEM setup that requires an OEM sysext image now. The update first happens with the inbuilt Omaha kolet server which uses the fallback logic but then flatcar-update is used for the second update to supply the OEM payload directly.
How to use
See scripts PR: flatcar/scripts#1016
Testing done
Manual and on Jenkins