-
Notifications
You must be signed in to change notification settings - Fork 40
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
[RFE] Add harness packages for Fedora 36 and RHEL 9 #158
Comments
As far as I knew, the harness packages were not available at https://beaker-project.org/yum/harness/ mostly because RHEL9 and F36 were not GA, thus the packages could not be released. Nevertheless, RHEL9 and F36 both GAed on May. It seems that Beaker is on a maintenance state nowadays, but it still has support inside Red Hat. Thus, I think it is just a matter of the request reaching the correct Beaker engineer at Red Hat. Maybe @StykMartin or @cbouchar knows who to forward these requests nowadays? |
I was keeping all packages in upstream up to date with OS releases. Lately, I wasn't able to find time to make a new build. |
@StykMartin Any update on this? I still don't see the packages for those distros available |
Is your feature request related to a problem? Please describe.
Importing the Fedora 36 and RHEL 9 distros works fine and they appear in beaker but provisioning with them always fails because it couldn't find the repo containing harness packages for the distro.
Describe the solution you'd like
It would be nice if there were officially supported harness packages for these distros in the beaker-project.org/yum/harness repository so that you can simply run
beaker-repo-update
and import them automatically. It says in the docs that you can point it at the harness-testing repo to get harness packages that are release candidates instead but neither Fedora 36 or RHEL 9 are in there currently. Fedora 36 has been out for a little while now and 37 is on the way so it would be nice to be able to use them in future provisioning to test on newer distros.Describe alternatives you've considered
It seems like you could substitute in another http hosted repository when using the
beaker-repo-update
command with the-b
flag but this is undesirable as it depends on whoever may be hosting the repository to maintain it.The text was updated successfully, but these errors were encountered: