-
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 arbitrary kickstart file injection into ISOs (HMS-3879) #4135
Add support for arbitrary kickstart file injection into ISOs (HMS-3879) #4135
Conversation
d6a0d49
to
e068cac
Compare
Rebased on #4157 |
e068cac
to
078cbac
Compare
7ab0e49
to
c870e00
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.
LGTM
🤔 |
Seems the issue is actually
|
The osbuild repo (and CI building RPMs) probably uses newer rpmrepo snapshots with newer selinux-policy package. |
ah of course, didn't think of that. Thanks! |
Pulled in #4147 |
c870e00
to
d9f510d
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.
😍
Also found the issue that I noticed here: #4147 (comment) |
6433b8f
to
7551bb8
Compare
@achilleas-k osbuild/images#705 breaks the "weldr api distro alias" test case, because it relies on the existence of |
Would it make sense to change the alias test to read /etc/os-release? That way we could build any image type, not rely on SAP, and read the |
IMO no, because that file comes from the RPM and it will not really tell you which distro version composer used when generating the manifest. The DNF vars file in SAP images is really the only thing that gets baked into the image and reflects the distro version used by composer. IOW, if the |
Right, we want to make sure the internal distro object and code path is correct regardless of repos. Gotcha. |
Added a config to the test that overrides the RHEL-8 alias. Small question for follow-up, but I wonder if it's necessary to be building the images here. I realise end-to-end testing is good, but maybe for this particular feature it's enough to just generate a manifest and check that we have a dnf config stage with the releasever set appropriately and save ourselves some testing time. |
Distro aliases is a feature of composer, so you can't really test it in the |
Right. I wasn't thinking of moving it to images, but maybe we could do something like cancel the build and inspect the manifest. Anyway, a discussion for another time. |
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.
👍
f763dc0
to
91d91ca
Compare
Pushed again. Had to fix the RHEL 8.8 runner name for the alias test ( |
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.
🤞
--- updated-dependencies: - dependency-name: cloud.google.com/go/compute dependency-type: direct:production update-type: version-update:semver-minor dependency-group: go-deps - dependency-name: cloud.google.com/go/storage dependency-type: direct:production update-type: version-update:semver-minor dependency-group: go-deps - dependency-name: github.com/aws/aws-sdk-go dependency-type: direct:production update-type: version-update:semver-minor dependency-group: go-deps - dependency-name: github.com/hashicorp/go-retryablehttp dependency-type: direct:production update-type: version-update:semver-patch dependency-group: go-deps - dependency-name: github.com/openshift-online/ocm-sdk-go dependency-type: direct:production update-type: version-update:semver-patch dependency-group: go-deps - dependency-name: github.com/osbuild/images dependency-type: direct:production update-type: version-update:semver-minor dependency-group: go-deps - dependency-name: github.com/prometheus/client_golang dependency-type: direct:production update-type: version-update:semver-patch dependency-group: go-deps - dependency-name: github.com/vmware/govmomi dependency-type: direct:production update-type: version-update:semver-patch dependency-group: go-deps - dependency-name: golang.org/x/oauth2 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: go-deps - dependency-name: golang.org/x/sys dependency-type: direct:production update-type: version-update:semver-minor dependency-group: go-deps - dependency-name: google.golang.org/api dependency-type: direct:production update-type: version-update:semver-minor dependency-group: go-deps ... Signed-off-by: dependabot[bot] <[email protected]>
Pulling in (among others): - osbuild/images#700 - Blueprint User customization change required. - osbuild/images#705
openssl gets installed as a dependency of the osbuild-composer-tests but it might not update openssh at the same time, which can cause a version mismatch when running ssh-keygen: OpenSSL version mismatch. Built against 30000000, you have 30200010 This is currently happening in CentOS Stream 9 so let's make sure openssh is up to date before running ssh-keygen.
The test relies on the existence of the /etc/dnf/vars/releasever file and the value it specifies. In SAP images, this file specifies the locked release version for the system and it is written by the image definition itself. This makes it a good candidate for ensuring we are using the correct distro version when building the image. However, RHEL 8.10 SAP images don't lock the distro version because 8.10 is the last minor version in the RHEL 8 cycle. Let's override the alias for RHEL 8 to point to 8.8, which is a version that should contain a releasever. The exact value we use isn't important. What we are testing here is the mechanism for resolving aliases.
- Change the alias example at the top of the file to use RHEL 9 -> 9.4 instead of 8 -> 8.10 which is no longer true for the test. - Fix some comment typos. - Clean trailing whitespaces.
91d91ca
to
f409390
Compare
Describe the new installer.kickstart customization that allows users to inject their own custom kickstart content into an ISO build. See osbuild/osbuild-composer#4135
Describe the new installer.kickstart customization that allows users to inject their own custom kickstart content into an ISO build. See osbuild/osbuild-composer#4135
Pulling in (primarily):