hrmm

so if the name is puppet-agent.service, the drop in must be puppet-agent.service.d/$override.conf

if you define it as puppet.service.d/$override.conf systemd will recognize it and complain it hasn't loaded, but will never load it

we had that with the rh-postgresql12-postgresql.service which aliased postgresql.service and found out our drop ins weren't being loaded, but systemd did say all the time it wanted a systemctl daemon-reload

besides "our own personal stuff" do you know of modules that manage the service/override for the puppet agent ?

I'm trying to get a feeling for how bad it would be if we don't revert vs if we do

This message was deleted.

https://github.com/theforeman/puppet-puppet/blob/36da0e10c3716fb6ca9d8daf149294e0d15acb71/manifests/params.pp#L278-L279 would need to be changed to become AIO and OS version dependent, which I'd prefer to avoid

right

thanks

https://github.com/theforeman/foreman/blob/2b7fc448fb3baf9e9b9d513be15c889e24076d5c/app/views/unattended/provisioning_templates/snippet/puppet_setup.erb#L176-L186 that probably continues working if there's an alias, but not 100% sure

ewoud: what about the package name

in debian 12 "puppet" will still be around, but as a transition package that pulls in puppet-agent

lavamind: https://github.com/theforeman/puppet-puppet/blob/36da0e10c3716fb6ca9d8daf149294e0d15acb71/manifests/params.pp#L270-L276 is what we have

I wouldn't mind if we end up standardizing on puppet-agent everywhere and can suggest the same thing in Fedora(/EPEL)

puppetlabs's puppet is puppet-agent

so ok

ewoud: I can standardize that on arch as well!

bastelfreak: sounds good

I hope to wrap up your PRs this week; next week we plan to do module releases for Foreman 3.6, which is also a good time to a major version one

like your renaming

does Foreman 3.6 gain el9 support?

ewoud: it seems "puppet resource service puppet ensure=running" does not work if puppet.service is an alias to puppet-agent.service

"Error: /Service[puppet]/ensure: change from 'stopped' to 'running' failed: Systemd start for puppet failed!"

Lumiere_: if you mean to run it on EL9; no and https://community.theforeman.org/t/path-to-ruby-3-0-3-1-el9-and-ubuntu-22-04/30295 is the long version

lavamind: hmm, that's also not great then

yeah

like I said earlier today: all software is a mess :(

thank you! that is helpful, we were looking at skipping el8 entirely, but with this we're going to have to push an el8 image just for katello :D

Could I get a review on https://github.com/voxpupuli/facterdb/pull/261 ?