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_082727405.pp.oSax9x Last 10 lines of output were: May 06 08:27:49 centos7-64-puppet7.example.com zabbix_proxy[6826]: One child process died (PID:6830,exitcode/signal:1). Exiting ... May 06 08:27:51 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:27:51 centos7-64-puppet7.example.com systemd[1]: Failed to start Zabbix Proxy. May 06 08:27:51 centos7-64-puppet7.example.com systemd[1]: Unit zabbix-proxy.service entered failed state. May 06 08:27:51 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 21.48 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_082751282.pp.nJxL6V Last 10 lines of output were: May 06 08:28:04 centos7-64-puppet7.example.com zabbix_proxy[7001]: required mandatory version: 05000000 May 06 08:28:04 centos7-64-puppet7.example.com zabbix_proxy[7001]: proxy #0 started [main process] May 06 08:28:04 centos7-64-puppet7.example.com zabbix_proxy[7005]: proxy #1 started [configuration syncer #1] May 06 08:28:04 centos7-64-puppet7.example.com zabbix_proxy[7001]: One child process died (PID:7005,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: Applied catalog in 13.12 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 6.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 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_082806874.pp.lKDrQN Last 10 lines of output were: May 06 08:28:22 centos7-64-puppet7.example.com systemd[1]: zabbix-proxy.service holdoff time over, scheduling restart. May 06 08:28:22 centos7-64-puppet7.example.com systemd[1]: Stopped Zabbix Proxy. May 06 08:28:22 centos7-64-puppet7.example.com systemd[1]: Starting Zabbix Proxy... May 06 08:28:22 centos7-64-puppet7.example.com zabbix_proxy[7209]: zabbix_proxy [7209]: unknown parameter "StartODBCPollers" in config file "/etc/zabbix/zabbix_proxy.conf", line 342 May 06 08:28:22 centos7-64-puppet7.example.com systemd[1]: zabbix-proxy.service: control process exited, code=exited status=1 �[mNotice: /Stage[main]/Zabbix::Proxy/Service[zabbix-proxy]: Triggered 'refresh' from 1 event Info: Class[Zabbix::Proxy]: Unscheduling all events on Class[Zabbix::Proxy] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 13.26 seconds Shared Example Group: "an idempotent resource" called from ./spec/acceptance/proxy_spec.rb:33

zabbix::proxy class deploys a zabbix 6.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_082822447.pp.ZzwfJx Last 10 lines of output were: 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. May 06 08:28:22 centos7-64-puppet7.example.com systemd[1]: zabbix-proxy.service holdoff time over, scheduling restart. May 06 08:28:22 centos7-64-puppet7.example.com systemd[1]: Stopped Zabbix Proxy. May 06 08:28:22 centos7-64-puppet7.example.com systemd[1]: Starting Zabbix Proxy... May 06 08:28:22 centos7-64-puppet7.example.com zabbix_proxy[7209]: zabbix_proxy [7209]: unknown parameter "StartODBCPollers" in config file "/etc/zabbix/zabbix_proxy.conf", line 342 May 06 08:28:22 centos7-64-puppet7.example.com systemd[1]: zabbix-proxy.service: control process exited, code=exited status=1 �[mNotice: Applied catalog in 11.16 seconds Shared Example Group: "an idempotent resource" called from ./spec/acceptance/proxy_spec.rb:33

zabbix::proxy class deploys a zabbix 6.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 6.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