Canceling since a higher priority waiting request for '363/merge' exists

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 upgrades to 9.2.0.1 Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'almalinux8-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_125943006.pp.nPSVUE Last 10 lines of output were: Mar 23 12:58:05 almalinux8-64-puppet7.example.com bash[2234]: chown: cannot access '/sys/fs/cgroup/memory/actions_job/b35dc0b8183caf3bbd86daf74500edd760e271709ddcb6bd4f48618c3a6b1019/actions_job/b35dc0b8183caf3bbd86daf74500edd760e271709ddcb6bd4f48618c3a6b1019/init.scope/system.slice/Splunkd.service': No such file or directory Mar 23 12:58:05 almalinux8-64-puppet7.example.com systemd[1]: Started Systemd service file for Splunk, generated by 'splunk enable boot-start'. Mar 23 12:58:05 almalinux8-64-puppet7.example.com splunk[2231]: Checking http port [8000]: open Mar 23 12:58:05 almalinux8-64-puppet7.example.com splunk[2231]: Checking mgmt port [8089]: open Mar 23 12:58:05 almalinux8-64-puppet7.example.com splunk[2231]: Checking appserver port [127.0.0.1:8065]: open Mar 23 12:58:05 almalinux8-64-puppet7.example.com splunk[2231]: Checking kvstore port [8191]: open Info: Class[Splunk::Enterprise]: Unscheduling all events on Class[Splunk::Enterprise] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 49.42 seconds

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 Service "Splunkd" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "Splunkd" to be enabled

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 Service "Splunkd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "Splunkd" to be running

The operation was canceled.

Canceling since a higher priority waiting request for '363/merge' exists

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 upgrades to 9.2.0.1 Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'ubuntu2004-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_125849696.pp.NTA7xS Last 10 lines of output were: Mar 23 12:57:05 ubuntu2004-64-puppet7.example.com systemd[1]: Started Systemd service file for Splunk, generated by 'splunk enable boot-start'. Mar 23 12:57:05 ubuntu2004-64-puppet7.example.com splunk[1777]: Checking http port [8000]: open Mar 23 12:57:05 ubuntu2004-64-puppet7.example.com splunk[1777]: Checking mgmt port [8089]: open Mar 23 12:57:05 ubuntu2004-64-puppet7.example.com splunk[1777]: Checking appserver port [127.0.0.1:8065]: open Mar 23 12:57:05 ubuntu2004-64-puppet7.example.com splunk[1777]: Checking kvstore port [8191]: open Mar 23 12:57:06 ubuntu2004-64-puppet7.example.com splunk[1811]: Checking configuration... Done. Info: Class[Splunk::Enterprise]: Unscheduling all events on Class[Splunk::Enterprise] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 80.12 seconds

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 Service "Splunkd" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "Splunkd" to be enabled

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 Service "Splunkd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "Splunkd" to be running

The operation was canceled.

Canceling since a higher priority waiting request for '363/merge' exists

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 upgrades to 9.2.0.1 Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'ubuntu2204-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_125838459.pp.h75i7r Last 10 lines of output were: Mar 23 12:56:55 ubuntu2204-64-puppet7.example.com systemd[1]: Started Systemd service file for Splunk, generated by 'splunk enable boot-start'. Mar 23 12:56:55 ubuntu2204-64-puppet7.example.com splunk[1743]: Checking http port [8000]: open Mar 23 12:56:55 ubuntu2204-64-puppet7.example.com splunk[1743]: Checking mgmt port [8089]: open Mar 23 12:56:55 ubuntu2204-64-puppet7.example.com splunk[1743]: Checking appserver port [127.0.0.1:8065]: open Mar 23 12:56:56 ubuntu2204-64-puppet7.example.com splunk[1743]: Checking kvstore port [8191]: open Mar 23 12:56:56 ubuntu2204-64-puppet7.example.com splunk[1777]: Checking configuration... Done. Info: Class[Splunk::Enterprise]: Unscheduling all events on Class[Splunk::Enterprise] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 78.28 seconds

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 Service "Splunkd" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "Splunkd" to be enabled

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 Service "Splunkd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "Splunkd" to be running

The operation was canceled.

Canceling since a higher priority waiting request for '363/merge' exists

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 upgrades to 9.2.0.1 Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'almalinux8-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_125930549.pp.dGC4Je Last 10 lines of output were: Mar 23 12:57:50 almalinux8-64-puppet8.example.com bash[2244]: chown: cannot access '/sys/fs/cgroup/memory/actions_job/ffe649369f9a613d06aade313770c22c7b47a6467f814571252995582f66209a/actions_job/ffe649369f9a613d06aade313770c22c7b47a6467f814571252995582f66209a/init.scope/system.slice/Splunkd.service': No such file or directory Mar 23 12:57:50 almalinux8-64-puppet8.example.com systemd[1]: Started Systemd service file for Splunk, generated by 'splunk enable boot-start'. Mar 23 12:57:50 almalinux8-64-puppet8.example.com splunk[2241]: Checking http port [8000]: open Mar 23 12:57:50 almalinux8-64-puppet8.example.com splunk[2241]: Checking mgmt port [8089]: open Mar 23 12:57:51 almalinux8-64-puppet8.example.com splunk[2241]: Checking appserver port [127.0.0.1:8065]: open Mar 23 12:57:51 almalinux8-64-puppet8.example.com splunk[2241]: Checking kvstore port [8191]: open Info: Class[Splunk::Enterprise]: Unscheduling all events on Class[Splunk::Enterprise] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 45.76 seconds

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 Service "Splunkd" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "Splunkd" to be enabled

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 Service "Splunkd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "Splunkd" to be running

The operation was canceled.

Canceling since a higher priority waiting request for '363/merge' exists

Canceling since a higher priority waiting request for '363/merge' exists

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 upgrades to 9.2.0.1 Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'centos9-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_125821316.pp.iCACez Last 10 lines of output were: Mar 23 12:56:16 centos9-64-puppet7.example.com systemd[1]: Stopped Systemd service file for Splunk, generated by 'splunk enable boot-start'. Mar 23 12:56:38 centos9-64-puppet7.example.com systemd[1]: /etc/systemd/system/Splunkd.service:25: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon. Mar 23 12:56:38 centos9-64-puppet7.example.com systemd[1]: /etc/systemd/system/Splunkd.service:26: Unit uses MemoryLimit=; please use MemoryMax= instead. Support for MemoryLimit= will be removed soon. Mar 23 12:56:39 centos9-64-puppet7.example.com systemd[1]: /etc/systemd/system/Splunkd.service:25: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon. Mar 23 12:56:39 centos9-64-puppet7.example.com systemd[1]: /etc/systemd/system/Splunkd.service:26: Unit uses MemoryLimit=; please use MemoryMax= instead. Support for MemoryLimit= will be removed soon. Mar 23 12:56:39 centos9-64-puppet7.example.com systemd[1]: Starting Systemd service file for Splunk, generated by 'splunk enable boot-start'... Info: Class[Splunk::Enterprise]: Unscheduling all events on Class[Splunk::Enterprise] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 47.08 seconds

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 upgrades to 9.2.0.1 Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'centos8-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_125837664.pp.8wuxTA Last 10 lines of output were: Mar 23 12:56:56 centos8-64-puppet8.example.com systemd[1]: Started Systemd service file for Splunk, generated by 'splunk enable boot-start'. Mar 23 12:56:56 centos8-64-puppet8.example.com splunk[2376]: Checking http port [8000]: open Mar 23 12:56:56 centos8-64-puppet8.example.com splunk[2376]: Checking mgmt port [8089]: open Mar 23 12:56:56 centos8-64-puppet8.example.com splunk[2376]: Checking appserver port [127.0.0.1:8065]: open Mar 23 12:56:56 centos8-64-puppet8.example.com splunk[2376]: Checking kvstore port [8191]: open Mar 23 12:56:56 centos8-64-puppet8.example.com splunk[2463]: Checking configuration... Done. Info: Class[Splunk::Enterprise]: Unscheduling all events on Class[Splunk::Enterprise] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 46.80 seconds

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 Service "Splunkd" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "Splunkd" to be enabled

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 Service "Splunkd" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "Splunkd" to be enabled

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 Service "Splunkd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "Splunkd" to be running

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 Service "Splunkd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "Splunkd" to be running

The operation was canceled.

The operation was canceled.

Canceling since a higher priority waiting request for '363/merge' exists

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 upgrades to 9.2.0.1 Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'debian10-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_125856231.pp.9czx0o Last 10 lines of output were: Mar 23 12:57:09 debian10-64-puppet8.example.com bash[2167]: chown: cannot access '/sys/fs/cgroup/memory/actions_job/72801a6962a21c3a892dc93141ba89ada139fa9c24880933536e388d6b625731/actions_job/72801a6962a21c3a892dc93141ba89ada139fa9c24880933536e388d6b625731/init.scope/system.slice/Splunkd.service': No such file or directory Mar 23 12:57:09 debian10-64-puppet8.example.com systemd[1]: Started Systemd service file for Splunk, generated by 'splunk enable boot-start'. Mar 23 12:57:09 debian10-64-puppet8.example.com splunk[2163]: Checking http port [8000]: open Mar 23 12:57:09 debian10-64-puppet8.example.com splunk[2163]: Checking mgmt port [8089]: open Mar 23 12:57:10 debian10-64-puppet8.example.com splunk[2163]: Checking appserver port [127.0.0.1:8065]: open Mar 23 12:57:10 debian10-64-puppet8.example.com splunk[2163]: Checking kvstore port [8191]: open Info: Class[Splunk::Enterprise]: Unscheduling all events on Class[Splunk::Enterprise] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 78.57 seconds

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 Service "Splunkd" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "Splunkd" to be enabled

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 Service "Splunkd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "Splunkd" to be running

The operation was canceled.

Canceling since a higher priority waiting request for '363/merge' exists

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 upgrades to 9.2.0.1 Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'debian10-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_125840983.pp.SchTgt Last 10 lines of output were: Mar 23 12:56:58 debian10-64-puppet7.example.com bash[2157]: chown: cannot access '/sys/fs/cgroup/memory/actions_job/25b0a5c67f181ca2793d21055dba484db41ebc44a5acb980af84143843c0d4c7/actions_job/25b0a5c67f181ca2793d21055dba484db41ebc44a5acb980af84143843c0d4c7/init.scope/system.slice/Splunkd.service': No such file or directory Mar 23 12:56:58 debian10-64-puppet7.example.com systemd[1]: Started Systemd service file for Splunk, generated by 'splunk enable boot-start'. Mar 23 12:56:58 debian10-64-puppet7.example.com splunk[2153]: Checking http port [8000]: open Mar 23 12:56:58 debian10-64-puppet7.example.com splunk[2153]: Checking mgmt port [8089]: open Mar 23 12:56:58 debian10-64-puppet7.example.com splunk[2153]: Checking appserver port [127.0.0.1:8065]: open Mar 23 12:56:58 debian10-64-puppet7.example.com splunk[2153]: Checking kvstore port [8191]: open Info: Class[Splunk::Enterprise]: Unscheduling all events on Class[Splunk::Enterprise] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 75.99 seconds

Canceling since a higher priority waiting request for '363/merge' exists

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 Service "Splunkd" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "Splunkd" to be enabled

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 upgrades to 9.2.0.1 Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'rocky8-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_125941023.pp.lYX5js Last 10 lines of output were: Mar 23 12:58:00 rocky8-64-puppet7.example.com bash[2121]: chown: cannot access '/sys/fs/cgroup/memory/actions_job/33905b9bd3b91c3d3ef8b676fed9065ced026cbd076a076d28f3a8f177204732/actions_job/33905b9bd3b91c3d3ef8b676fed9065ced026cbd076a076d28f3a8f177204732/init.scope/system.slice/Splunkd.service': No such file or directory Mar 23 12:58:00 rocky8-64-puppet7.example.com systemd[1]: Started Systemd service file for Splunk, generated by 'splunk enable boot-start'. Mar 23 12:58:00 rocky8-64-puppet7.example.com splunk[2118]: Checking http port [8000]: open Mar 23 12:58:00 rocky8-64-puppet7.example.com splunk[2118]: Checking mgmt port [8089]: open Mar 23 12:58:01 rocky8-64-puppet7.example.com splunk[2118]: Checking appserver port [127.0.0.1:8065]: open Mar 23 12:58:01 rocky8-64-puppet7.example.com splunk[2118]: Checking kvstore port [8191]: open Info: Class[Splunk::Enterprise]: Unscheduling all events on Class[Splunk::Enterprise] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 49.40 seconds

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 Service "Splunkd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "Splunkd" to be running

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 Service "Splunkd" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "Splunkd" to be enabled

The operation was canceled.

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 Service "Splunkd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "Splunkd" to be running

The operation was canceled.

Canceling since a higher priority waiting request for '363/merge' exists

Canceling since a higher priority waiting request for '363/merge' exists

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 upgrades to 9.2.0.1 Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'centos8-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_125840854.pp.IENokh Last 10 lines of output were: Mar 23 12:57:02 centos8-64-puppet7.example.com systemd[1]: Started Systemd service file for Splunk, generated by 'splunk enable boot-start'. Mar 23 12:57:02 centos8-64-puppet7.example.com splunk[2298]: Checking http port [8000]: open Mar 23 12:57:02 centos8-64-puppet7.example.com splunk[2298]: Checking mgmt port [8089]: open Mar 23 12:57:02 centos8-64-puppet7.example.com splunk[2298]: Checking appserver port [127.0.0.1:8065]: open Mar 23 12:57:02 centos8-64-puppet7.example.com splunk[2298]: Checking kvstore port [8191]: open Mar 23 12:57:02 centos8-64-puppet7.example.com splunk[2385]: Checking configuration... Done. Info: Class[Splunk::Enterprise]: Unscheduling all events on Class[Splunk::Enterprise] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 48.40 seconds

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 upgrades to 9.2.0.1 Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'rocky9-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_125823164.pp.TZ6Acd Last 10 lines of output were: Mar 23 12:56:12 rocky9-64-puppet7.example.com systemd[1]: Stopped Systemd service file for Splunk, generated by 'splunk enable boot-start'. Mar 23 12:56:39 rocky9-64-puppet7.example.com systemd[1]: /etc/systemd/system/Splunkd.service:25: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon. Mar 23 12:56:39 rocky9-64-puppet7.example.com systemd[1]: /etc/systemd/system/Splunkd.service:26: Unit uses MemoryLimit=; please use MemoryMax= instead. Support for MemoryLimit= will be removed soon. Mar 23 12:56:39 rocky9-64-puppet7.example.com systemd[1]: /etc/systemd/system/Splunkd.service:25: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon. Mar 23 12:56:39 rocky9-64-puppet7.example.com systemd[1]: /etc/systemd/system/Splunkd.service:26: Unit uses MemoryLimit=; please use MemoryMax= instead. Support for MemoryLimit= will be removed soon. Mar 23 12:56:39 rocky9-64-puppet7.example.com systemd[1]: Starting Systemd service file for Splunk, generated by 'splunk enable boot-start'... Info: Class[Splunk::Enterprise]: Unscheduling all events on Class[Splunk::Enterprise] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 46.99 seconds

Canceling since a higher priority waiting request for '363/merge' exists

Canceling since a higher priority waiting request for '363/merge' exists

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 Service "Splunkd" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "Splunkd" to be enabled

Canceling since a higher priority waiting request for '363/merge' exists

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 Service "Splunkd" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "Splunkd" to be enabled

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 upgrades to 9.2.0.1 Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'rocky8-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_125946177.pp.B33aa2 Last 10 lines of output were: Mar 23 12:58:03 rocky8-64-puppet8.example.com bash[2131]: chown: cannot access '/sys/fs/cgroup/memory/actions_job/99560dcc1166a7399dda9d9694dc9eeb48a08f413e99fc447e48b2dce38e0ef8/actions_job/99560dcc1166a7399dda9d9694dc9eeb48a08f413e99fc447e48b2dce38e0ef8/init.scope/system.slice/Splunkd.service': No such file or directory Mar 23 12:58:03 rocky8-64-puppet8.example.com systemd[1]: Started Systemd service file for Splunk, generated by 'splunk enable boot-start'. Mar 23 12:58:03 rocky8-64-puppet8.example.com splunk[2128]: Checking http port [8000]: open Mar 23 12:58:03 rocky8-64-puppet8.example.com splunk[2128]: Checking mgmt port [8089]: open Mar 23 12:58:03 rocky8-64-puppet8.example.com splunk[2128]: Checking appserver port [127.0.0.1:8065]: open Mar 23 12:58:03 rocky8-64-puppet8.example.com splunk[2128]: Checking kvstore port [8191]: open Info: Class[Splunk::Enterprise]: Unscheduling all events on Class[Splunk::Enterprise] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 48.92 seconds

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 upgrades to 9.2.0.1 Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'centos7-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_125837194.pp.zsBKnR Last 10 lines of output were: Mar 23 12:56:52 centos7-64-puppet8.example.com splunk[1704]: Checking appserver port [127.0.0.1:8065]: open Mar 23 12:56:52 centos7-64-puppet8.example.com splunk[1704]: Checking kvstore port [8191]: open Mar 23 12:56:52 centos7-64-puppet8.example.com splunk[1704]: Checking configuration... Done. Mar 23 12:56:52 centos7-64-puppet8.example.com splunk[1704]: New certs have been generated in '/opt/splunk/etc/auth'. Mar 23 12:56:52 centos7-64-puppet8.example.com splunk[1704]: Checking critical directories... Done Mar 23 12:56:52 centos7-64-puppet8.example.com splunk[1704]: Checking indexes... Info: Class[Splunk::Enterprise]: Unscheduling all events on Class[Splunk::Enterprise] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 52.12 seconds

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 Service "Splunkd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "Splunkd" to be running

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 upgrades to 9.2.0.1 Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'centos7-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_125852735.pp.O6WrXG Last 10 lines of output were: Mar 23 12:57:08 centos7-64-puppet7.example.com splunk[1705]: Checking appserver port [127.0.0.1:8065]: open Mar 23 12:57:08 centos7-64-puppet7.example.com splunk[1705]: Checking kvstore port [8191]: open Mar 23 12:57:08 centos7-64-puppet7.example.com splunk[1705]: Checking configuration... Done. Mar 23 12:57:08 centos7-64-puppet7.example.com splunk[1705]: New certs have been generated in '/opt/splunk/etc/auth'. Mar 23 12:57:08 centos7-64-puppet7.example.com splunk[1705]: Checking critical directories... Done Mar 23 12:57:08 centos7-64-puppet7.example.com splunk[1705]: Checking indexes... Info: Class[Splunk::Enterprise]: Unscheduling all events on Class[Splunk::Enterprise] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 52.67 seconds

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 Service "Splunkd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "Splunkd" to be running

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 Service "Splunkd" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "Splunkd" to be enabled

The operation was canceled.

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 Service "Splunkd" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "Splunkd" to be enabled

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 Service "Splunkd" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "Splunkd" to be enabled

The operation was canceled.

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 Service "Splunkd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "Splunkd" to be running

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 Service "Splunkd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "Splunkd" to be running

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 Service "Splunkd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "Splunkd" to be running

The operation was canceled.

The operation was canceled.

The operation was canceled.

Canceling since a higher priority waiting request for '363/merge' exists

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 upgrades to 9.2.0.1 Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'almalinux9-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_125814423.pp.uK6FY5 Last 10 lines of output were: Mar 23 12:56:06 almalinux9-64-puppet8.example.com systemd[1]: Stopped Systemd service file for Splunk, generated by 'splunk enable boot-start'. Mar 23 12:56:30 almalinux9-64-puppet8.example.com systemd[1]: /etc/systemd/system/Splunkd.service:25: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon. Mar 23 12:56:30 almalinux9-64-puppet8.example.com systemd[1]: /etc/systemd/system/Splunkd.service:26: Unit uses MemoryLimit=; please use MemoryMax= instead. Support for MemoryLimit= will be removed soon. Mar 23 12:56:30 almalinux9-64-puppet8.example.com systemd[1]: /etc/systemd/system/Splunkd.service:25: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon. Mar 23 12:56:30 almalinux9-64-puppet8.example.com systemd[1]: /etc/systemd/system/Splunkd.service:26: Unit uses MemoryLimit=; please use MemoryMax= instead. Support for MemoryLimit= will be removed soon. Mar 23 12:56:30 almalinux9-64-puppet8.example.com systemd[1]: Starting Systemd service file for Splunk, generated by 'splunk enable boot-start'... Info: Class[Splunk::Enterprise]: Unscheduling all events on Class[Splunk::Enterprise] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 49.58 seconds

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 Service "Splunkd" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "Splunkd" to be enabled

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 Service "Splunkd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "Splunkd" to be running

The operation was canceled.

Canceling since a higher priority waiting request for '363/merge' exists

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 upgrades to 9.2.0.1 Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'ubuntu2004-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_125902472.pp.QuRu7o Last 10 lines of output were: Mar 23 12:57:18 ubuntu2004-64-puppet8.example.com systemd[1]: Started Systemd service file for Splunk, generated by 'splunk enable boot-start'. Mar 23 12:57:18 ubuntu2004-64-puppet8.example.com splunk[1776]: Checking http port [8000]: open Mar 23 12:57:18 ubuntu2004-64-puppet8.example.com splunk[1776]: Checking mgmt port [8089]: open Mar 23 12:57:18 ubuntu2004-64-puppet8.example.com splunk[1776]: Checking appserver port [127.0.0.1:8065]: open Mar 23 12:57:18 ubuntu2004-64-puppet8.example.com splunk[1776]: Checking kvstore port [8191]: open Mar 23 12:57:19 ubuntu2004-64-puppet8.example.com splunk[1810]: Checking configuration... Done. Info: Class[Splunk::Enterprise]: Unscheduling all events on Class[Splunk::Enterprise] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 75.21 seconds

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 Service "Splunkd" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "Splunkd" to be enabled

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 Service "Splunkd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "Splunkd" to be running

The operation was canceled.

Canceling since a higher priority waiting request for '363/merge' exists

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 upgrades to 9.2.0.1 Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'ubuntu2204-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_125844745.pp.fVfM7S Last 10 lines of output were: Mar 23 12:57:02 ubuntu2204-64-puppet8.example.com systemd[1]: Started Systemd service file for Splunk, generated by 'splunk enable boot-start'. Mar 23 12:57:02 ubuntu2204-64-puppet8.example.com splunk[1751]: Checking http port [8000]: open Mar 23 12:57:02 ubuntu2204-64-puppet8.example.com splunk[1751]: Checking mgmt port [8089]: open Mar 23 12:57:02 ubuntu2204-64-puppet8.example.com splunk[1751]: Checking appserver port [127.0.0.1:8065]: open Mar 23 12:57:02 ubuntu2204-64-puppet8.example.com splunk[1751]: Checking kvstore port [8191]: open Mar 23 12:57:03 ubuntu2204-64-puppet8.example.com splunk[1785]: Checking configuration... Done. Info: Class[Splunk::Enterprise]: Unscheduling all events on Class[Splunk::Enterprise] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 77.88 seconds

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 Service "Splunkd" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "Splunkd" to be enabled

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 Service "Splunkd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "Splunkd" to be running

The operation was canceled.

Canceling since a higher priority waiting request for '363/merge' exists

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 upgrades to 9.2.0.1 Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'rocky9-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_125817922.pp.3fvqI8 Last 10 lines of output were: Mar 23 12:56:09 rocky9-64-puppet8.example.com systemd[1]: Stopped Systemd service file for Splunk, generated by 'splunk enable boot-start'. Mar 23 12:56:31 rocky9-64-puppet8.example.com systemd[1]: /etc/systemd/system/Splunkd.service:25: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon. Mar 23 12:56:31 rocky9-64-puppet8.example.com systemd[1]: /etc/systemd/system/Splunkd.service:26: Unit uses MemoryLimit=; please use MemoryMax= instead. Support for MemoryLimit= will be removed soon. Mar 23 12:56:31 rocky9-64-puppet8.example.com systemd[1]: /etc/systemd/system/Splunkd.service:25: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon. Mar 23 12:56:31 rocky9-64-puppet8.example.com systemd[1]: /etc/systemd/system/Splunkd.service:26: Unit uses MemoryLimit=; please use MemoryMax= instead. Support for MemoryLimit= will be removed soon. Mar 23 12:56:31 rocky9-64-puppet8.example.com systemd[1]: Starting Systemd service file for Splunk, generated by 'splunk enable boot-start'... Info: Class[Splunk::Enterprise]: Unscheduling all events on Class[Splunk::Enterprise] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 49.62 seconds

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 Service "Splunkd" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "Splunkd" to be enabled

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 Service "Splunkd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "Splunkd" to be running

The operation was canceled.

Canceling since a higher priority waiting request for '363/merge' exists

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 upgrades to 9.2.0.1 Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'almalinux9-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_125821163.pp.AF2NzW Last 10 lines of output were: Mar 23 12:56:11 almalinux9-64-puppet7.example.com systemd[1]: Stopped Systemd service file for Splunk, generated by 'splunk enable boot-start'. Mar 23 12:56:33 almalinux9-64-puppet7.example.com systemd[1]: /etc/systemd/system/Splunkd.service:25: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon. Mar 23 12:56:33 almalinux9-64-puppet7.example.com systemd[1]: /etc/systemd/system/Splunkd.service:26: Unit uses MemoryLimit=; please use MemoryMax= instead. Support for MemoryLimit= will be removed soon. Mar 23 12:56:33 almalinux9-64-puppet7.example.com systemd[1]: /etc/systemd/system/Splunkd.service:25: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon. Mar 23 12:56:33 almalinux9-64-puppet7.example.com systemd[1]: /etc/systemd/system/Splunkd.service:26: Unit uses MemoryLimit=; please use MemoryMax= instead. Support for MemoryLimit= will be removed soon. Mar 23 12:56:33 almalinux9-64-puppet7.example.com systemd[1]: Starting Systemd service file for Splunk, generated by 'splunk enable boot-start'... Info: Class[Splunk::Enterprise]: Unscheduling all events on Class[Splunk::Enterprise] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 50.34 seconds

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 Service "Splunkd" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "Splunkd" to be enabled

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 Service "Splunkd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "Splunkd" to be running

The operation was canceled.

Canceling since a higher priority waiting request for '363/merge' exists

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 upgrades to 9.2.0.1 Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'centos9-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_125821247.pp.f9Crmf Last 10 lines of output were: Mar 23 12:56:17 centos9-64-puppet8.example.com systemd[1]: Stopped Systemd service file for Splunk, generated by 'splunk enable boot-start'. Mar 23 12:56:39 centos9-64-puppet8.example.com systemd[1]: /etc/systemd/system/Splunkd.service:25: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon. Mar 23 12:56:39 centos9-64-puppet8.example.com systemd[1]: /etc/systemd/system/Splunkd.service:26: Unit uses MemoryLimit=; please use MemoryMax= instead. Support for MemoryLimit= will be removed soon. Mar 23 12:56:39 centos9-64-puppet8.example.com systemd[1]: /etc/systemd/system/Splunkd.service:25: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon. Mar 23 12:56:39 centos9-64-puppet8.example.com systemd[1]: /etc/systemd/system/Splunkd.service:26: Unit uses MemoryLimit=; please use MemoryMax= instead. Support for MemoryLimit= will be removed soon. Mar 23 12:56:39 centos9-64-puppet8.example.com systemd[1]: Starting Systemd service file for Splunk, generated by 'splunk enable boot-start'... Info: Class[Splunk::Enterprise]: Unscheduling all events on Class[Splunk::Enterprise] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 46.69 seconds

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 Service "Splunkd" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "Splunkd" to be enabled

splunk enterprise class Upgrading splunk enterprise from 9.1.0 to 9.2.0.1 Service "Splunkd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "Splunkd" to be running