zabbix::server 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 'debian12-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_153342767.S52iyw.pp Last 10 lines of output were: [select userid from users limit 1] Jul 03 15:34:08 debian12-64-puppet7.example.com zabbix_server[12307]: cannot use database "zabbix_server": database is not a Zabbix database Jul 03 15:34:10 debian12-64-puppet7.example.com systemd[1]: zabbix-server.service: Can't open PID file /run/zabbix/zabbix_server.pid (yet?) after start: No such file or directory Jul 03 15:34:10 debian12-64-puppet7.example.com systemd[1]: zabbix-server.service: Failed with result 'protocol'. Jul 03 15:34:10 debian12-64-puppet7.example.com systemd[1]: Failed to start zabbix-server.service - Zabbix Server. �[mNotice: /Stage[main]/Zabbix::Server/Service[zabbix-server]: Triggered 'refresh' from 4 events Info: Class[Zabbix::Server]: Unscheduling all events on Class[Zabbix::Server] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 24.36 seconds Shared Example Group: "an idempotent resource" called from ./spec/acceptance/server_spec.rb:10

zabbix::server 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 'debian12-64-puppet7.example.com' exited with 4 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_153410695.ezjEDJ.pp Last 10 lines of output were: Jul 03 15:34:20 debian12-64-puppet7.example.com zabbix_server[12796]: [Z3005] query failed: [0] PGRES_FATAL_ERROR:ERROR: relation "users" does not exist LINE 1: select userid from users limit 1 ^ [select userid from users limit 1] Jul 03 15:34:20 debian12-64-puppet7.example.com zabbix_server[12796]: cannot use database "zabbix_server": database is not a Zabbix database Jul 03 15:34:22 debian12-64-puppet7.example.com systemd[1]: zabbix-server.service: Can't open PID file /run/zabbix/zabbix_server.pid (yet?) after start: No such file or directory Jul 03 15:34:22 debian12-64-puppet7.example.com systemd[1]: zabbix-server.service: Failed with result 'protocol'. Jul 03 15:34:22 debian12-64-puppet7.example.com systemd[1]: Failed to start zabbix-server.service - Zabbix Server. �[mNotice: Applied catalog in 8.46 seconds Shared Example Group: "an idempotent resource" called from ./spec/acceptance/server_spec.rb:10

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

zabbix::server class deploys a zabbix 7.0 server 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 'debian12-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_153422918.QzaOji.pp Last 10 lines of output were: Jul 03 15:34:32 debian12-64-puppet7.example.com zabbix_server[13632]: SNMP monitoring: YES Jul 03 15:34:32 debian12-64-puppet7.example.com zabbix_server[13632]: IPMI monitoring: YES Jul 03 15:34:32 debian12-64-puppet7.example.com zabbix_server[13632]: Web monitoring: YES Jul 03 15:34:32 debian12-64-puppet7.example.com zabbix_server[13632]: VMware monitoring: YES Jul 03 15:34:32 debian12-64-puppet7.example.com zabbix_server[13632]: SMTP authentication: YES �[mNotice: /Stage[main]/Zabbix::Server/Service[zabbix-server]: Triggered 'refresh' from 1 event Info: Class[Zabbix::Server]: Unscheduling all events on Class[Zabbix::Server] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 8.34 seconds Shared Example Group: "an idempotent resource" called from ./spec/acceptance/server_spec.rb:42

zabbix::server class deploys a zabbix 7.0 server 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 'debian12-64-puppet7.example.com' exited with 4 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_153435040.uMVNao.pp Last 10 lines of output were: Jul 03 15:34:32 debian12-64-puppet7.example.com systemd[1]: Starting zabbix-server.service - Zabbix Server... Jul 03 15:34:32 debian12-64-puppet7.example.com zabbix_server[13632]: Starting Zabbix Server. Zabbix 6.0.31 (revision b6d93755a1b). Jul 03 15:34:32 debian12-64-puppet7.example.com zabbix_server[13632]: ****** Enabled features ****** Jul 03 15:34:32 debian12-64-puppet7.example.com zabbix_server[13632]: SNMP monitoring: YES Jul 03 15:34:32 debian12-64-puppet7.example.com zabbix_server[13632]: IPMI monitoring: YES Jul 03 15:34:32 debian12-64-puppet7.example.com zabbix_server[13632]: Web monitoring: YES Jul 03 15:34:32 debian12-64-puppet7.example.com zabbix_server[13632]: VMware monitoring: YES Jul 03 15:34:32 debian12-64-puppet7.example.com zabbix_server[13632]: SMTP authentication: YES �[mNotice: Applied catalog in 7.99 seconds Shared Example Group: "an idempotent resource" called from ./spec/acceptance/server_spec.rb:42

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