Eric Helms
Eric Helms
> > What am I missing? > > 2025-03-03 08:22:54 [ERROR ] [configure] Could not find resource 'File[/etc/pki/katello/certs/katello-default-ca.crt]' in parameter 'require' (file: /usr/share/foreman-installer/modules/certs/manifests/foreman_proxy.pp, line: 129) on node almalinux9.tanso.example.com > >...
> I thought we wanted to track the nightly version instead. I am more leaning towards nightly is more work than it's worth due to the slower update cycle, and...
> I think the biggest challenge is that you'd constantly need to change the default branch. We saw with pulpcore-packaging that people forget. Git clones also don't automatically pick that...
Thanks for tackling that! I'll let you do the honors of updating https://community.theforeman.org/t/could-the-candlepin-gpg-keys-be-published-somewhere-http-reachable/38193 with the news
@ekohl I think this should go in before branch
I can download it with `vagrant-2.3.4-3.fc39.noarch`, but the `/vagrant` issue is harder. Could we opt for a different strategy using `bootc switch` on a regular VMs?
I am guessing the same will need to happen for the rpm serving and thus I should copy this model?
This solution works for me as an approach. Thanks for taking a look.
A migration spec for this would be great to have. Example: https://github.com/theforeman/foreman-installer/blob/develop/spec/migrations/20240328125552_reset_puppetserver_ciphers_spec.rb