Skip to content

Release 6.0.0

Release 6.0.0 #427

Triggered via pull request September 4, 2023 11:48
@evgenievgeni
synchronize #372
release-6.0.0
Status Failure
Total duration 4m 27s
Artifacts

ci.yml

on: pull_request
Puppet  /  Static validations
41s
Puppet / Static validations
Matrix: Puppet / acceptance
Matrix: Puppet / unit
Puppet  /  Test suite
0s
Puppet / Test suite
Fit to window
Zoom out
Zoom in

Annotations

10 errors
Puppet / 7 - OracleLinux 7: spec/acceptance/resolved_spec.rb#L7
systemd with manage_resolved true configure systemd resolved works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'oracle7-64-puppet7.example.com' exited with 4 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_115109940.pp.nxMXCG Last 10 lines of output were: systemd = 219-78.0.7.el7_9.3 Available: systemd-219-78.0.7.el7_9.5.x86_64 (ol7_latest) systemd = 219-78.0.7.el7_9.5 Available: systemd-219-78.0.9.el7_9.5.x86_64 (ol7_latest) systemd = 219-78.0.9.el7_9.5 Available: systemd-219-78.0.9.el7_9.7.x86_64 (ol7_latest) systemd = 219-78.0.9.el7_9.7 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest �[mNotice: Applied catalog in 1.18 seconds
Puppet / 7 - OracleLinux 7: spec/acceptance/resolved_spec.rb#L21
systemd with manage_resolved true configure systemd resolved Service "systemd-resolved" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "systemd-resolved" to be running
Puppet / 7 - OracleLinux 7: spec/acceptance/resolved_spec.rb#L22
systemd with manage_resolved true configure systemd resolved Service "systemd-resolved" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "systemd-resolved" to be enabled
Puppet / 7 - OracleLinux 7: spec/acceptance/resolved_spec.rb#L27
systemd with manage_resolved true configure systemd stopped works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'oracle7-64-puppet7.example.com' exited with 4 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_115113981.pp.85Oo3A Last 10 lines of output were: systemd = 219-78.0.7.el7_9.3 Available: systemd-219-78.0.7.el7_9.5.x86_64 (ol7_latest) systemd = 219-78.0.7.el7_9.5 Available: systemd-219-78.0.9.el7_9.5.x86_64 (ol7_latest) systemd = 219-78.0.9.el7_9.5 Available: systemd-219-78.0.9.el7_9.7.x86_64 (ol7_latest) systemd = 219-78.0.9.el7_9.7 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest �[mNotice: Applied catalog in 1.18 seconds
Puppet / 7 - OracleLinux 7
Process completed with exit code 1.
Puppet / 8 - OracleLinux 7: spec/acceptance/resolved_spec.rb#L7
systemd with manage_resolved true configure systemd resolved works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'oracle7-64-puppet8.example.com' exited with 4 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_115115294.pp.5SELui Last 10 lines of output were: systemd = 219-78.0.7.el7_9.3 Available: systemd-219-78.0.7.el7_9.5.x86_64 (ol7_latest) systemd = 219-78.0.7.el7_9.5 Available: systemd-219-78.0.9.el7_9.5.x86_64 (ol7_latest) systemd = 219-78.0.9.el7_9.5 Available: systemd-219-78.0.9.el7_9.7.x86_64 (ol7_latest) systemd = 219-78.0.9.el7_9.7 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest �[mNotice: Applied catalog in 1.20 seconds
Puppet / 8 - OracleLinux 7: spec/acceptance/resolved_spec.rb#L21
systemd with manage_resolved true configure systemd resolved Service "systemd-resolved" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "systemd-resolved" to be running
Puppet / 8 - OracleLinux 7: spec/acceptance/resolved_spec.rb#L22
systemd with manage_resolved true configure systemd resolved Service "systemd-resolved" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "systemd-resolved" to be enabled
Puppet / 8 - OracleLinux 7: spec/acceptance/resolved_spec.rb#L27
systemd with manage_resolved true configure systemd stopped works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'oracle7-64-puppet8.example.com' exited with 4 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_115122439.pp.NnUtBb Last 10 lines of output were: systemd = 219-78.0.7.el7_9.3 Available: systemd-219-78.0.7.el7_9.5.x86_64 (ol7_latest) systemd = 219-78.0.7.el7_9.5 Available: systemd-219-78.0.9.el7_9.5.x86_64 (ol7_latest) systemd = 219-78.0.9.el7_9.5 Available: systemd-219-78.0.9.el7_9.7.x86_64 (ol7_latest) systemd = 219-78.0.9.el7_9.7 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest �[mNotice: Applied catalog in 1.20 seconds
Puppet / 8 - OracleLinux 7
Process completed with exit code 1.