Release 6.0.0 #422
traylenator
This run and associated checks have been archived and are scheduled for deletion.
Learn more about checks retention
ci.yml
on: pull_request
Puppet
/
Static validations
32s
Matrix: Puppet / acceptance
Matrix: Puppet / unit
Puppet
/
Test suite
0s
Annotations
11 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_134503363.pp.P7WftJ
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.16 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_134507327.pp.4ZdQTx
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.16 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_134512688.pp.4iaQQj
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.16 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_134518700.pp.FlG4F4
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.16 seconds
|
|
Puppet / 8 - OracleLinux 7
Process completed with exit code 1.
|
|
Puppet / 7 - CentOS 8
Process completed with exit code 1.
|