fail2ban when package purged behaves like an idempotent resource applies a second time without changes Failure/Error: raise CommandFailure, "Host '#{self}' exited with #{result.exit_code} running:\n #{cmdline}\nLast #{@options[:trace_limit]} lines of output were:\n#{result.formatted_output(@options[:trace_limit])}" Beaker::Host::CommandFailure: Host 'almalinux9-64-puppet7.example.com' exited with 2 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_131403859.7NheWM.pp Last 10 lines of output were: �[mNotice: Compiled catalog for almalinux9-64-puppet7.example.com in environment production in 0.05 seconds Info: Using environment 'production' Info: Applying configuration version '1727097245' �[mNotice: /Stage[main]/Fail2ban::Config/File[fail2ban.dir]: Not removing directory; use 'force' to override �[mNotice: /Stage[main]/Fail2ban::Config/File[fail2ban.dir]/ensure: removed Info: fail2ban.dir: Scheduling refresh of Service[fail2ban] Info: Class[Fail2ban::Config]: Scheduling refresh of Class[Fail2ban::Service] Info: Class[Fail2ban::Service]: Scheduling refresh of Service[fail2ban] �[mNotice: /Stage[main]/Fail2ban::Service/Service[fail2ban]: Triggered 'refresh' from 2 events �[mNotice: Applied catalog in 0.21 seconds Shared Example Group: "an idempotent resource" called from ./spec/acceptance/fail2ban_spec.rb:79