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

Support EL9 #823

Merged
merged 2 commits into from
Jan 10, 2024
Merged

Support EL9 #823

merged 2 commits into from
Jan 10, 2024

Conversation

ekohl
Copy link
Member

@ekohl ekohl commented Jan 3, 2024

No description provided.

@ekohl
Copy link
Member Author

ekohl commented Jan 3, 2024

This now fails to retrieve the foreman-plugins repository (but probably also foreman because https://github.com/theforeman/puppet-foreman/blob/557c952c1a519cb7126dfa6267eb1a5c4707880d/manifests/repos/yum.pp#L22 includes release, which isn't a thing on staging). Once we fix that, I think this will fail:
https://github.com/theforeman/puppet-foreman/blob/557c952c1a519cb7126dfa6267eb1a5c4707880d/manifests/repo.pp#L24-L31

We don't intend to consume modules in the initial release, so I think that should be patched:theforeman/puppet-foreman#1147

@ekohl
Copy link
Member Author

ekohl commented Jan 4, 2024

Submitted the first part separate: #824

@ekohl
Copy link
Member Author

ekohl commented Jan 4, 2024

@evgeni & @ehelms: should we create a release -> foreman symlink on stagingyum for the time being? Then we can at least proceed with this, without having to run the entire pipeline every time. Or should we temporarily modify it to directly consume https://copr.fedorainfracloud.org/coprs/g/theforeman/foreman-nightly-staging directly instead?

@evgeni
Copy link
Member

evgeni commented Jan 4, 2024

How about a foreman->releases sysmlink on yum.tfm as the first step to unifying the repo structure?

@ekohl
Copy link
Member Author

ekohl commented Jan 4, 2024

How about a foreman->releases sysmlink on yum.tfm as the first step to unifying the repo structure?

I thought about the same, but I wondered about CDN caching efficiency. For staging that's less of a concern.

@evgeni
Copy link
Member

evgeni commented Jan 4, 2024

136 examples, 71 failures

That's half of the suite passing. I like!

@ekohl
Copy link
Member Author

ekohl commented Jan 4, 2024

And the failing ones are plugins, which makes sense since it doesn't set up that repository at all

@evgeni
Copy link
Member

evgeni commented Jan 5, 2024

ansible, container_gateway and pulp plugins are still missing, the rest should show up fine

Edit:
136 examples, 39 failures

  • mosquitto (the daemon) is missing
  • puppet-foreman_scap_client is missing
  • ansible-collection-theforeman-* is missing

@ekohl
Copy link
Member Author

ekohl commented Jan 6, 2024

mosquitto (the daemon) is missing

I submitted voxpupuli/puppet-mosquitto#45 but realized they pull mosquitto from EPEL.

@evgeni
Copy link
Member

evgeni commented Jan 9, 2024

136 examples, 8 failures

all ansible

TIL: we do not have smart_proxy_container_gateway tests? :D

@evgeni
Copy link
Member

evgeni commented Jan 9, 2024

#825

Fixes: d3156b3 ("Switch to voxpupuli-acceptance-1.0")
@ekohl ekohl marked this pull request as ready for review January 10, 2024 13:25
@evgeni evgeni merged commit 5409839 into theforeman:master Jan 10, 2024
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants