zabbix::proxy class default parameters behaves like an idempotent resource applies with no errors 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 'centos7-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_082739612.pp.e6BGQ4 Last 10 lines of output were: May 06 08:28:04 centos7-64-puppet7.example.com zabbix_proxy[6842]: One child process died (PID:6846,exitcode/signal:1). Exiting ... May 06 08:28:06 centos7-64-puppet7.example.com systemd[1]: Can't open PID file /run/zabbix/zabbix_proxy.pid (yet?) after start: No such file or directory May 06 08:28:06 centos7-64-puppet7.example.com systemd[1]: Failed to start Zabbix Proxy. May 06 08:28:06 centos7-64-puppet7.example.com systemd[1]: Unit zabbix-proxy.service entered failed state. May 06 08:28:06 centos7-64-puppet7.example.com systemd[1]: zabbix-proxy.service failed. �[mNotice: /Stage[main]/Zabbix::Proxy/Service[zabbix-proxy]: Triggered 'refresh' from 4 events Info: Class[Zabbix::Proxy]: Unscheduling all events on Class[Zabbix::Proxy] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 24.83 seconds Shared Example Group: "an idempotent resource" called from ./spec/acceptance/proxy_spec.rb:10

zabbix::proxy class default parameters 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 'centos7-64-puppet7.example.com' exited with 4 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_082806777.pp.mWiLkp Last 10 lines of output were: May 06 08:28:19 centos7-64-puppet7.example.com zabbix_proxy[7017]: current database version (mandatory/optional): 05000000/05000007 May 06 08:28:19 centos7-64-puppet7.example.com zabbix_proxy[7017]: required mandatory version: 05000000 May 06 08:28:20 centos7-64-puppet7.example.com zabbix_proxy[7017]: proxy #0 started [main process] May 06 08:28:20 centos7-64-puppet7.example.com zabbix_proxy[7017]: One child process died (PID:7021,exitcode/signal:1). Exiting ... May 06 08:28:21 centos7-64-puppet7.example.com systemd[1]: Can't open PID file /run/zabbix/zabbix_proxy.pid (yet?) after start: No such file or directory May 06 08:28:21 centos7-64-puppet7.example.com systemd[1]: Failed to start Zabbix Proxy. May 06 08:28:21 centos7-64-puppet7.example.com systemd[1]: Unit zabbix-proxy.service entered failed state. May 06 08:28:21 centos7-64-puppet7.example.com systemd[1]: zabbix-proxy.service failed. �[mNotice: Applied catalog in 13.09 seconds Shared Example Group: "an idempotent resource" called from ./spec/acceptance/proxy_spec.rb:10

zabbix::proxy class default parameters Service "zabbix-proxy" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "zabbix-proxy" to be running

zabbix::proxy class default parameters Service "zabbix-proxy" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "zabbix-proxy" to be enabled

zabbix::proxy class deploys a zabbix 5.0 proxy behaves like an idempotent resource applies with no errors 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 'centos7-64-puppet7.example.com' exited with 4 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_082822324.pp.HQ4npH Last 10 lines of output were: May 06 08:28:21 centos7-64-puppet7.example.com systemd[1]: Unit zabbix-proxy.service entered failed state. May 06 08:28:21 centos7-64-puppet7.example.com systemd[1]: zabbix-proxy.service failed. May 06 08:28:35 centos7-64-puppet7.example.com systemd[1]: zabbix-proxy.service holdoff time over, scheduling restart. May 06 08:28:35 centos7-64-puppet7.example.com systemd[1]: Stopped Zabbix Proxy. May 06 08:28:35 centos7-64-puppet7.example.com systemd[1]: Starting Zabbix Proxy... May 06 08:28:35 centos7-64-puppet7.example.com zabbix_proxy[7219]: Starting Zabbix Proxy (active) [centos7-64-puppet7.example.com]. Zabbix 5.0.42 (revision e25e9cfa36a). May 06 08:28:35 centos7-64-puppet7.example.com zabbix_proxy[7219]: **** Enabled features **** May 06 08:28:35 centos7-64-puppet7.example.com zabbix_proxy[7219]: SNMP monitoring: YES �[mNotice: Applied catalog in 13.01 seconds Shared Example Group: "an idempotent resource" called from ./spec/acceptance/proxy_spec.rb:33

zabbix::proxy class deploys a zabbix 5.0 proxy 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 'centos7-64-puppet7.example.com' exited with 4 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_082837639.pp.OUo12o Last 10 lines of output were: May 06 08:28:21 centos7-64-puppet7.example.com systemd[1]: Unit zabbix-proxy.service entered failed state. May 06 08:28:21 centos7-64-puppet7.example.com systemd[1]: zabbix-proxy.service failed. May 06 08:28:35 centos7-64-puppet7.example.com systemd[1]: zabbix-proxy.service holdoff time over, scheduling restart. May 06 08:28:35 centos7-64-puppet7.example.com systemd[1]: Stopped Zabbix Proxy. May 06 08:28:35 centos7-64-puppet7.example.com systemd[1]: Starting Zabbix Proxy... May 06 08:28:35 centos7-64-puppet7.example.com zabbix_proxy[7219]: Starting Zabbix Proxy (active) [centos7-64-puppet7.example.com]. Zabbix 5.0.42 (revision e25e9cfa36a). May 06 08:28:35 centos7-64-puppet7.example.com zabbix_proxy[7219]: **** Enabled features **** May 06 08:28:35 centos7-64-puppet7.example.com zabbix_proxy[7219]: SNMP monitoring: YES �[mNotice: Applied catalog in 12.98 seconds Shared Example Group: "an idempotent resource" called from ./spec/acceptance/proxy_spec.rb:33

zabbix::proxy class deploys a zabbix 5.0 proxy Service "zabbix-proxy" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "zabbix-proxy" to be running

zabbix::proxy class deploys a zabbix 5.0 proxy Service "zabbix-proxy" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "zabbix-proxy" to be enabled