-
Notifications
You must be signed in to change notification settings - Fork 107
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
Add support for advanced partitioning customizations (COMPOSER-2399) #4535
Add support for advanced partitioning customizations (COMPOSER-2399) #4535
Conversation
df59325
to
423fb63
Compare
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.
Thanks for this PR, I have a very silly question inline, it comes down to if we can find a way to avoid some of the duplication with the images code that are currently present in this PR.
I need to update image-info to handle btrfs subvolumes and ignore swap partitions when mounting filesystems. |
Let's try to standardize on the |
|
083694d
to
4527f9d
Compare
4527f9d
to
cbf8577
Compare
Rebased (onto #4543) and fixed conflicts. |
eb2e697
to
d112ccb
Compare
https://gitlab.com/redhat/services/products/image-builder/ci/osbuild-composer/-/pipelines/1653730001
|
Add DiskCustomization and all its children to the internal blueprint. Add the conversion to the images counterpart to the Convert() function.
Move the creation of the blueprint to a function. We'll then add a separate blueprint function for the new, alternative partitioning customization.
Version 94 of osbuild-composer is over a year old now. It should be fine to test these unconditionally.
d112ccb
to
9e07001
Compare
Add separate blueprint creation functions, one for each partitioning layout: - disk-plain - disk-lvm - disk-btrfs (Fedora only) The existing 'filesystem' blueprint is also kept. Each function also sets the $EXPECTED_MOUNTPOINTS variable for the mountpoint check that happens after the build.
Remove incorrect comment (not an ostree image). Add a greenprint for depsolving since it can take some time for that to run and it makes more sense than pausing output on "Preparing blueprint".
9e07001
to
57e4008
Compare
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.
I've added one comment, but won't block on it...
Run filesystem.sh with all the valid arguments for the customization type.
Can be useful for troubleshooting and tracing test logs.
57e4008
to
52e8d60
Compare
The repository issues were probably because I didn't mark any runners with the internal network variable in |
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.
🤞
Filesystem tests are now passing. But I'm still seeing fewer jobs than the ones I listed in the CI config: filesystem.sh:
extends: .integration
parallel:
matrix:
- CUSTOMIZATION_TYPE: "disk-btrfs"
RUNNER:
- aws/fedora-40-x86_64
- CUSTOMIZATION_TYPE: "filesystem"
RUNNER:
- aws/rhel-8.10-ga-x86_64
INTERNAL_NETWORK: ["true"]
- CUSTOMIZATION_TYPE: "disk-plain"
RUNNER:
- aws/rhel-9.4-ga-x86_64
- aws/rhel-10.0-nightly-x86_64
INTERNAL_NETWORK: ["true"]
- CUSTOMIZATION_TYPE: "disk-lvm"
RUNNER:
- aws/rhel-9.6-nightly-x86_64
INTERNAL_NETWORK: ["true"]
- CUSTOMIZATION_TYPE: "disk-lvm"
RUNNER:
- aws/centos-stream-9-x86_64
- CUSTOMIZATION_TYPE: "filesystem"
RUNNER:
- aws/centos-stream-10-x86_64
variables:
SCRIPT: filesystem.sh ${CUSTOMIZATION_TYPE} but in the pipeline I'm only seeing:
EDIT: .ga_rules_all:
rules:
- if: '$CI_PIPELINE_SOURCE == "schedule" && $RUNNER =~ /[\S]+rhel-[\S]+-(?:(?:ga)|(?:eus))[\S]+/ && $NIGHTLY == "false"' |
I spoke with @ondrejbudai and we decided that the gitlab CI config could use a lot of simplification and also that we should merge this as is and sort out any other config combinations separately. |
This PR enables the
disk
customizations in osbuild-composer.Tests for the new blueprint configurations have been added to filesystem.sh.
This pull request includes: