vault 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 2 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_180412973.AVNntp.pp Last 10 lines of output were: Info: Loading facts Info: Loading facts Info: Loading facts Info: Loading facts �[mNotice: Compiled catalog for centos7-64-puppet7.example.com in environment production in 0.17 seconds Info: Using environment 'production' Info: Applying configuration version '1717092254' �[mNotice: /Stage[main]/Vault::Service/Service[vault]/ensure: ensure changed 'stopped' to 'running' Info: /Stage[main]/Vault::Service/Service[vault]: Unscheduling refresh on Service[vault] �[mNotice: Applied catalog in 0.14 seconds Shared Example Group: "an idempotent resource" called from ./spec/acceptance/class_spec.rb:7

vault class default parameters Command "systemctl list-units" stdout is expected to include "vault.service" Failure/Error: its(:stdout) { is_expected.to include 'vault.service' } expected " UNIT ...oaded but inactive units, too.\nTo show all installed unit files use 'systemctl list-unit-files'.\n" to include "vault.service" Diff: @@ -1,118 +1,235 @@ -vault.service + UNIT LOAD ACTIVE SUB DESCRIPTION + proc-sys-fs-binfmt_misc.automount loaded active waiting Arbitrary Executable File Formats File System Automount Point + sys-devices-LNXSYSTM:00-LNXSYBUS:00-PNP0A03:00-device:07-VMBUS:01-00000000\x2d0000\x2d8899\x2d0000\x2d000000000000-host0-target0:0:0-0:0:0:0-block-sda-sda1.device loaded active plugged Virtual_Disk cloudimg-rootfs + sys-devices-LNXSYSTM:00-LNXSYBUS:00-PNP0A03:00-device:07-VMBUS:01-00000000\x2d0000\x2d8899\x2d0000\x2d000000000000-host0-target0:0:0-0:0:0:0-block-sda-sda14.device loaded active plugged Virtual_Disk 14 + sys-devices-LNXSYSTM:00-LNXSYBUS:00-PNP0A03:00-device:07-VMBUS:01-00000000\x2d0000\x2d8899\x2d0000\x2d000000000000-host0-target0:0:0-0:0:0:0-block-sda-sda15.device loaded active plugged Virtual_Disk UEFI + sys-devices-LNXSYSTM:00-LNXSYBUS:00-PNP0A03:00-device:07-VMBUS:01-00000000\x2d0000\x2d8899\x2d0000\x2d000000000000-host0-target0:0:0-0:0:0:0-block-sda.device loaded active plugged Virtual_Disk + sys-devices-LNXSYSTM:00-LNXSYBUS:00-PNP0A03:00-device:07-VMBUS:01-00000000\x2d0001\x2d8899\x2d0000\x2d000000000000-host1-target1:0:1-1:0:1:0-block-sdb-sdb1.device loaded active plugged Virtual_Disk 1 + sys-devices-LNXSYSTM:00-LNXSYBUS:00-PNP0A03:00-device:07-VMBUS:01-00000000\x2d0001\x2d8899\x2d0000\x2d000000000000-host1-target1:0:1-1:0:1:0-block-sdb.device loaded active plugged Virtual_Disk + sys-devices-platform-serial8250-tty-ttyS10.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS10 + sys-devices-platform-serial8250-tty-ttyS11.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS11 + sys-devices-platform-serial8250-tty-ttyS12.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS12 + sys-devices-platform-serial8250-tty-ttyS13.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS13 + sys-devices-platform-serial8250-tty-ttyS14.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS14 + sys-devices-platform-serial8250-tty-ttyS15.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS15 + sys-devices-platform-serial8250-tty-ttyS16.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS16 + sys-devices-platform-serial8250-tty-ttyS17.device

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

vault class default parameters Port "8200" is expected to be listening on 127.0.0.1 with tcp Failure/Error: it { is_expected.to be_listening.on('127.0.0.1').with('tcp') } expected Port "8200" to be listening on 127.0.0.1 with tcp

vault class with package based setup 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 2 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_180425521.bF5ZAJ.pp Last 10 lines of output were: Info: Loading facts Info: Loading facts Info: Loading facts Info: Loading facts �[mNotice: Compiled catalog for centos7-64-puppet7.example.com in environment production in 0.08 seconds Info: Using environment 'production' Info: Applying configuration version '1717092267' �[mNotice: /Stage[main]/Vault::Service/Service[vault]/ensure: ensure changed 'stopped' to 'running' Info: /Stage[main]/Vault::Service/Service[vault]: Unscheduling refresh on Service[vault] �[mNotice: Applied catalog in 0.13 seconds Shared Example Group: "an idempotent resource" called from ./spec/acceptance/class_spec.rb:88

vault class with package based setup Service "vault" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "vault" to be running

vault class with package based setup Port "8200" is expected to be listening on 127.0.0.1 with tcp Failure/Error: it { is_expected.to be_listening.on('127.0.0.1').with('tcp') } expected Port "8200" to be listening on 127.0.0.1 with tcp