Skip to content
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

Validate OSTree options on RHEL10 #1034

Closed
wants to merge 1 commit into from

Conversation

bcl
Copy link
Contributor

@bcl bcl commented Nov 11, 2024

This check seems to have been lost in the initial commit of this file. Discovered while working on weldr-client tests running on RHEL10.

Related: RHEL-67056

This check seems to have been lost in the initial commit of this file.
Discovered while working on weldr-client tests running on RHEL10.

Related: RHEL-67056
@bcl bcl requested review from thozza and achilleas-k November 11, 2024 23:50
@bcl
Copy link
Contributor Author

bcl commented Nov 11, 2024

There may be other things missing from this file, it looks quite a bit different from the fedora and rhel9 versions but I can't tell what supposed to be there and what isn't -- other than this, which was caught by my weldr-client tests when I run it on RHEL10.

@achilleas-k
Copy link
Member

We're not supporting edge for RHEL 10, so it might be more appropriate for this check to return an error when ostree != nil right away.

@thozza
Copy link
Member

thozza commented Nov 27, 2024

I went ahead and implemented the check for all distros in #1071

@thozza
Copy link
Member

thozza commented Nov 28, 2024

I went ahead and implemented the check for all distros in #1071

The PR was merged, so any el10 image types should now generate an error if OSTree image options are provided. @bcl, are you okay with closing this PR?

@bcl
Copy link
Contributor Author

bcl commented Dec 2, 2024

Thanks!

@bcl bcl closed this Dec 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants