BIND 9.18 compatiblity on Ubuntu 20.04 #1046
Annotations
10 errors
vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-3.2.0/lib/voxpupuli/acceptance/examples.rb#L4
Scenario: install bind 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 'archlinuxrolling-64.example.com' exited with 6 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_165015339.oEzINX.pp
Last 10 lines of output were:
Error: Execution of '/usr/sbin/named-checkconf /etc/named.conf20240813-729-m52mg2' returned 1: /etc/named.options.conf:5: the 'dnssec-validation yes' option requires configured 'trust-anchors'; consider using 'dnssec-validation auto'.
Error: /Stage[main]/Dns::Config/Concat[/etc/named.conf]/File[/etc/named.conf]/content: change from '{sha256}e08a01d41b18bdb771d534daca99642314939aafdb088e5cfcf0ef2d33f8e7eb' to '{sha256}353117179538086a90c98f8a981a9a8a48ab3fd3804bd084fd9224d2f782ed46' failed: Execution of '/usr/sbin/named-checkconf /etc/named.conf20240813-729-m52mg2' returned 1: /etc/named.options.conf:5: the 'dnssec-validation yes' option requires configured 'trust-anchors'; consider using 'dnssec-validation auto'.
Info: Class[Dns::Config]: Unscheduling all events on Class[Dns::Config]
�[mNotice: /Stage[main]/Main/Dns::Zone[example.com]/File[/var/named/dynamic/db.example.com]/ensure: defined content as '{sha256}c18d2c8785bcc880340b663d2d40b9c16c2cd1eabf8ae08c4c63a8b515d00c99'
Info: /Stage[main]/Main/Dns::Zone[example.com]/File[/var/named/dynamic/db.example.com]: Scheduling refresh of Class[Dns::Service]
Info: Class[Dns::Service]: Unscheduling all events on Class[Dns::Service]
�[mNotice: /Stage[main]/Dns::Service/Service[named]: Dependency File[/etc/named.conf] has failures: true
Warning: /Stage[main]/Dns::Service/Service[named]: Skipping because of failed dependencies
Info: Stage[main]: Unscheduling all events on Stage[main]
�[mNotice: Applied catalog in 2.51 seconds
Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dns_spec.rb:4
|
vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-3.2.0/lib/voxpupuli/acceptance/examples.rb#L8
Scenario: install bind 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 'archlinuxrolling-64.example.com' exited with 4 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_165019454.7OzaxG.pp
Last 10 lines of output were:
�[mNotice: Compiled catalog for archlinuxrolling-64.example.com in environment production in 0.12 seconds
Info: Using environment 'production'
Info: Applying configuration version '1723567820'
Info: Computing checksum on file /etc/named.conf
Info: /Stage[main]/Dns::Config/Concat[/etc/named.conf]/File[/etc/named.conf]: Filebucketed /etc/named.conf to puppet with sum e08a01d41b18bdb771d534daca99642314939aafdb088e5cfcf0ef2d33f8e7eb
Error: Execution of '/usr/sbin/named-checkconf /etc/named.conf20240813-882-z7cmx3' returned 1: /etc/named.options.conf:5: the 'dnssec-validation yes' option requires configured 'trust-anchors'; consider using 'dnssec-validation auto'.
Error: /Stage[main]/Dns::Config/Concat[/etc/named.conf]/File[/etc/named.conf]/content: change from '{sha256}e08a01d41b18bdb771d534daca99642314939aafdb088e5cfcf0ef2d33f8e7eb' to '{sha256}353117179538086a90c98f8a981a9a8a48ab3fd3804bd084fd9224d2f782ed46' failed: Execution of '/usr/sbin/named-checkconf /etc/named.conf20240813-882-z7cmx3' returned 1: /etc/named.options.conf:5: the 'dnssec-validation yes' option requires configured 'trust-anchors'; consider using 'dnssec-validation auto'.
�[mNotice: /Stage[main]/Dns::Service/Service[named]: Dependency File[/etc/named.conf] has failures: true
Warning: /Stage[main]/Dns::Service/Service[named]: Skipping because of failed dependencies
�[mNotice: Applied catalog in 0.28 seconds
Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dns_spec.rb:4
|
spec/acceptance/dns_spec.rb#L21
Scenario: install bind Service "named" is expected to be enabled
Failure/Error: it { is_expected.to be_enabled }
expected Service "named" to be enabled
|
spec/acceptance/dns_spec.rb#L22
Scenario: install bind Service "named" is expected to be running
Failure/Error: it { is_expected.to be_running }
expected Service "named" to be running
|
spec/acceptance/dns_spec.rb#L30
Scenario: install bind Command "dig +short SOA example.com @localhost" stdout is expected to match "ns1.example.com. root.example.com. 1 86400 3600 604800 3600\n"
Failure/Error: its(:stdout) { is_expected.to match("ns1.example.com. root.example.com. 1 86400 3600 604800 3600\n") }
expected ";; communications error to ::1#53: connection refused\n;; communications error to ::1#53: connection...ed\n;; communications error to 127.0.0.1#53: connection refused\n;; no servers could be reached\n\n" to match "ns1.example.com. root.example.com. 1 86400 3600 604800 3600\n"
Diff:
@@ -1,5 +1,9 @@
-ns1.example.com. root.example.com. 1 86400 3600 604800 3600
+;; communications error to ::1#53: connection refused
+;; communications error to ::1#53: connection refused
+;; communications error to ::1#53: connection refused
+;; communications error to 127.0.0.1#53: connection refused
+;; no servers could be reached
|
vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-3.2.0/lib/voxpupuli/acceptance/examples.rb#L4
Scenario: install bind with logging enabled with logging enabled 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 'archlinuxrolling-64.example.com' exited with 6 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_165022650.AuQ9j3.pp
Last 10 lines of output were:
Info: Applying configuration version '1723567823'
Info: Computing checksum on file /etc/named.conf
Info: /Stage[main]/Dns::Config/Concat[/etc/named.conf]/File[/etc/named.conf]: Filebucketed /etc/named.conf to puppet with sum e08a01d41b18bdb771d534daca99642314939aafdb088e5cfcf0ef2d33f8e7eb
Error: Execution of '/usr/sbin/named-checkconf /etc/named.conf20240813-941-1euzgcr' returned 1: /etc/named.options.conf:5: the 'dnssec-validation yes' option requires configured 'trust-anchors'; consider using 'dnssec-validation auto'.
Error: /Stage[main]/Dns::Config/Concat[/etc/named.conf]/File[/etc/named.conf]/content: change from '{sha256}e08a01d41b18bdb771d534daca99642314939aafdb088e5cfcf0ef2d33f8e7eb' to '{sha256}1c1af875b332767dde002562b328ced992f46383b00d8f66a00bb9e913ed1607' failed: Execution of '/usr/sbin/named-checkconf /etc/named.conf20240813-941-1euzgcr' returned 1: /etc/named.options.conf:5: the 'dnssec-validation yes' option requires configured 'trust-anchors'; consider using 'dnssec-validation auto'.
�[mNotice: /Stage[main]/Dns::Logging/File[/var/log/named]/ensure: created
�[mNotice: /Stage[main]/Dns::Service/Service[named]: Dependency File[/etc/named.conf] has failures: true
Warning: /Stage[main]/Dns::Service/Service[named]: Skipping because of failed dependencies
Info: Stage[main]: Unscheduling all events on Stage[main]
�[mNotice: Applied catalog in 0.29 seconds
Shared Example Group: "an idempotent resource" called from ./spec/acceptance/logging_spec.rb:5
|
vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-3.2.0/lib/voxpupuli/acceptance/examples.rb#L8
Scenario: install bind with logging enabled with logging enabled 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 'archlinuxrolling-64.example.com' exited with 4 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_165024480.BkwkZ7.pp
Last 10 lines of output were:
�[mNotice: Compiled catalog for archlinuxrolling-64.example.com in environment production in 0.13 seconds
Info: Using environment 'production'
Info: Applying configuration version '1723567825'
Info: Computing checksum on file /etc/named.conf
Info: /Stage[main]/Dns::Config/Concat[/etc/named.conf]/File[/etc/named.conf]: Filebucketed /etc/named.conf to puppet with sum e08a01d41b18bdb771d534daca99642314939aafdb088e5cfcf0ef2d33f8e7eb
Error: Execution of '/usr/sbin/named-checkconf /etc/named.conf20240813-969-1oj54bt' returned 1: /etc/named.options.conf:5: the 'dnssec-validation yes' option requires configured 'trust-anchors'; consider using 'dnssec-validation auto'.
Error: /Stage[main]/Dns::Config/Concat[/etc/named.conf]/File[/etc/named.conf]/content: change from '{sha256}e08a01d41b18bdb771d534daca99642314939aafdb088e5cfcf0ef2d33f8e7eb' to '{sha256}1c1af875b332767dde002562b328ced992f46383b00d8f66a00bb9e913ed1607' failed: Execution of '/usr/sbin/named-checkconf /etc/named.conf20240813-969-1oj54bt' returned 1: /etc/named.options.conf:5: the 'dnssec-validation yes' option requires configured 'trust-anchors'; consider using 'dnssec-validation auto'.
�[mNotice: /Stage[main]/Dns::Service/Service[named]: Dependency File[/etc/named.conf] has failures: true
Warning: /Stage[main]/Dns::Service/Service[named]: Skipping because of failed dependencies
�[mNotice: Applied catalog in 0.29 seconds
Shared Example Group: "an idempotent resource" called from ./spec/acceptance/logging_spec.rb:5
|
spec/acceptance/logging_spec.rb#L38
Scenario: install bind with logging enabled with logging enabled Service "named" is expected to be enabled
Failure/Error: it { is_expected.to be_enabled }
expected Service "named" to be enabled
|
spec/acceptance/logging_spec.rb#L39
Scenario: install bind with logging enabled with logging enabled Service "named" is expected to be running
Failure/Error: it { is_expected.to be_running }
expected Service "named" to be running
|
spec/acceptance/logging_spec.rb#L47
Scenario: install bind with logging enabled with logging enabled Command "dig +short SOA example.com @localhost" stdout is expected to match "ns1.example.com. root.example.com. 1 86400 3600 604800 3600\n"
Failure/Error: its(:stdout) { is_expected.to match("ns1.example.com. root.example.com. 1 86400 3600 604800 3600\n") }
expected ";; communications error to ::1#53: connection refused\n;; communications error to ::1#53: connection...ed\n;; communications error to 127.0.0.1#53: connection refused\n;; no servers could be reached\n\n" to match "ns1.example.com. root.example.com. 1 86400 3600 604800 3600\n"
Diff:
@@ -1,5 +1,9 @@
-ns1.example.com. root.example.com. 1 86400 3600 604800 3600
+;; communications error to ::1#53: connection refused
+;; communications error to ::1#53: connection refused
+;; communications error to ::1#53: connection refused
+;; communications error to 127.0.0.1#53: connection refused
+;; no servers could be reached
|
This job failed
Loading