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_133218729.LO6TdI.pp Last 10 lines of output were: Error: Execution of '/usr/sbin/named-checkconf /etc/named.conf20250214-862-pcvl6' 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.conf20250214-862-pcvl6' 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.16 seconds Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dns_spec.rb:4

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_133222870.GXd8kI.pp Last 10 lines of output were: �[mNotice: Compiled catalog for archlinuxrolling-64.example.com in environment production in 0.11 seconds Info: Using environment 'production' Info: Applying configuration version '1739539944' 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.conf20250214-1137-1jrzn4f' 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.conf20250214-1137-1jrzn4f' 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.26 seconds Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dns_spec.rb:4

Scenario: install bind Service "named" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "named" to be enabled

Scenario: install bind Service "named" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "named" to be running

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...used\n;; communications error to 127.0.0.1#53: connection refused\n;; no servers could be reached\n" to match "ns1.example.com. root.example.com. 1 86400 3600 604800 3600\n" Diff: @@ -1 +1,5 @@ -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

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_133225464.ssW4JD.pp Last 10 lines of output were: Info: Applying configuration version '1739539947' 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.conf20250214-1310-gh6au' 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.conf20250214-1310-gh6au' 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.28 seconds Shared Example Group: "an idempotent resource" called from ./spec/acceptance/logging_spec.rb:5

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_133227622.KHDiGT.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 '1739539949' 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.conf20250214-1471-16ugk2r' 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.conf20250214-1471-16ugk2r' 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/logging_spec.rb:5

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

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

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...used\n;; communications error to 127.0.0.1#53: connection refused\n;; no servers could be reached\n" to match "ns1.example.com. root.example.com. 1 86400 3600 604800 3600\n" Diff: @@ -1 +1,5 @@ -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

Process completed with exit code 1.

Skipping EOL operating system FreeBSD 11

Cache not found for keys: setup-ruby-bundler-cache-v6-ubuntu-22.04-x64-ruby-3.2.7-wd-/home/runner/work/puppet-dns/puppet-dns-with--without-development:system_tests:release-only--v-1-Gemfile.lock-a61f0f320178d77b6789faa900bdb20898ce006e879433d0249118defad044d2, setup-ruby-bundler-cache-v6-ubuntu-22.04-x64-ruby-3.2.7-wd-/home/runner/work/puppet-dns/puppet-dns-with--without-development:system_tests:release-only--v-1-Gemfile.lock-

The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101

Cache not found for keys: setup-ruby-bundler-cache-v6-ubuntu-20.04-x64-ruby-3.2.7-wd-/home/runner/work/puppet-dns/puppet-dns-with--without-development:test:release-only--v-1-Gemfile.lock-ebac66d6ee5ce40635c58c7257e9ae743717905930392928fee773f20c831f56, setup-ruby-bundler-cache-v6-ubuntu-20.04-x64-ruby-3.2.7-wd-/home/runner/work/puppet-dns/puppet-dns-with--without-development:test:release-only--v-1-Gemfile.lock-

Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists

The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101

Cache not found for keys: setup-ruby-bundler-cache-v6-ubuntu-20.04-x64-ruby-3.2.7-wd-/home/runner/work/puppet-dns/puppet-dns-with--without-development:test:release-only--v-1-Gemfile.lock-ebac66d6ee5ce40635c58c7257e9ae743717905930392928fee773f20c831f56, setup-ruby-bundler-cache-v6-ubuntu-20.04-x64-ruby-3.2.7-wd-/home/runner/work/puppet-dns/puppet-dns-with--without-development:test:release-only--v-1-Gemfile.lock-

The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101

Cache not found for keys: setup-ruby-bundler-cache-v6-ubuntu-20.04-x64-ruby-3.2.7-wd-/home/runner/work/puppet-dns/puppet-dns-with--without-development:test:release-only--v-1-Gemfile.lock-ebac66d6ee5ce40635c58c7257e9ae743717905930392928fee773f20c831f56, setup-ruby-bundler-cache-v6-ubuntu-20.04-x64-ruby-3.2.7-wd-/home/runner/work/puppet-dns/puppet-dns-with--without-development:test:release-only--v-1-Gemfile.lock-

Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists

The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101

Cache not found for keys: setup-ruby-bundler-cache-v6-ubuntu-20.04-x64-ruby-3.2.7-wd-/home/runner/work/puppet-dns/puppet-dns-with--without-development:test:release-only--v-1-Gemfile.lock-ebac66d6ee5ce40635c58c7257e9ae743717905930392928fee773f20c831f56, setup-ruby-bundler-cache-v6-ubuntu-20.04-x64-ruby-3.2.7-wd-/home/runner/work/puppet-dns/puppet-dns-with--without-development:test:release-only--v-1-Gemfile.lock-

Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists

The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101

Cache not found for keys: setup-ruby-bundler-cache-v6-ubuntu-20.04-x64-ruby-3.2.7-wd-/home/runner/work/puppet-dns/puppet-dns-with--without-development:test:release-only--v-1-Gemfile.lock-ebac66d6ee5ce40635c58c7257e9ae743717905930392928fee773f20c831f56, setup-ruby-bundler-cache-v6-ubuntu-20.04-x64-ruby-3.2.7-wd-/home/runner/work/puppet-dns/puppet-dns-with--without-development:test:release-only--v-1-Gemfile.lock-

Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists

The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101

Cache not found for keys: setup-ruby-bundler-cache-v6-ubuntu-20.04-x64-ruby-3.2.7-wd-/home/runner/work/puppet-dns/puppet-dns-with--without-development:test:release-only--v-1-Gemfile.lock-ebac66d6ee5ce40635c58c7257e9ae743717905930392928fee773f20c831f56, setup-ruby-bundler-cache-v6-ubuntu-20.04-x64-ruby-3.2.7-wd-/home/runner/work/puppet-dns/puppet-dns-with--without-development:test:release-only--v-1-Gemfile.lock-

Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists

The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101

Cache not found for keys: setup-ruby-bundler-cache-v6-ubuntu-20.04-x64-ruby-3.2.7-wd-/home/runner/work/puppet-dns/puppet-dns-with--without-development:test:release-only--v-1-Gemfile.lock-ebac66d6ee5ce40635c58c7257e9ae743717905930392928fee773f20c831f56, setup-ruby-bundler-cache-v6-ubuntu-20.04-x64-ruby-3.2.7-wd-/home/runner/work/puppet-dns/puppet-dns-with--without-development:test:release-only--v-1-Gemfile.lock-

Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists

The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101

Cache not found for keys: setup-ruby-bundler-cache-v6-ubuntu-20.04-x64-ruby-3.2.7-wd-/home/runner/work/puppet-dns/puppet-dns-with--without-development:test:release-only--v-1-Gemfile.lock-ebac66d6ee5ce40635c58c7257e9ae743717905930392928fee773f20c831f56, setup-ruby-bundler-cache-v6-ubuntu-20.04-x64-ruby-3.2.7-wd-/home/runner/work/puppet-dns/puppet-dns-with--without-development:test:release-only--v-1-Gemfile.lock-

Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists

The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101

Cache not found for keys: setup-ruby-bundler-cache-v6-ubuntu-20.04-x64-ruby-3.2.7-wd-/home/runner/work/puppet-dns/puppet-dns-with--without-development:test:release-only--v-1-Gemfile.lock-ebac66d6ee5ce40635c58c7257e9ae743717905930392928fee773f20c831f56, setup-ruby-bundler-cache-v6-ubuntu-20.04-x64-ruby-3.2.7-wd-/home/runner/work/puppet-dns/puppet-dns-with--without-development:test:release-only--v-1-Gemfile.lock-

Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists

The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101

Cache not found for keys: setup-ruby-bundler-cache-v6-ubuntu-20.04-x64-ruby-3.2.7-wd-/home/runner/work/puppet-dns/puppet-dns-with--without-development:test:release-only--v-1-Gemfile.lock-ebac66d6ee5ce40635c58c7257e9ae743717905930392928fee773f20c831f56, setup-ruby-bundler-cache-v6-ubuntu-20.04-x64-ruby-3.2.7-wd-/home/runner/work/puppet-dns/puppet-dns-with--without-development:test:release-only--v-1-Gemfile.lock-

Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists

The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101

Cache not found for keys: setup-ruby-bundler-cache-v6-ubuntu-20.04-x64-ruby-3.2.7-wd-/home/runner/work/puppet-dns/puppet-dns-with--without-development:test:release-only--v-1-Gemfile.lock-ebac66d6ee5ce40635c58c7257e9ae743717905930392928fee773f20c831f56, setup-ruby-bundler-cache-v6-ubuntu-20.04-x64-ruby-3.2.7-wd-/home/runner/work/puppet-dns/puppet-dns-with--without-development:test:release-only--v-1-Gemfile.lock-

Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists

Cache not found for keys: setup-ruby-bundler-cache-v6-ubuntu-22.04-x64-ruby-2.7.8-wd-/home/runner/work/puppet-dns/puppet-dns-with--without-development:system_tests:release-only--v-1-Gemfile.lock-3af520616066688041071af924d0196e3d551e83afdfa0673212adea90bef9bb, setup-ruby-bundler-cache-v6-ubuntu-22.04-x64-ruby-2.7.8-wd-/home/runner/work/puppet-dns/puppet-dns-with--without-development:system_tests:release-only--v-1-Gemfile.lock-

The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101

Cache not found for keys: setup-ruby-bundler-cache-v6-ubuntu-20.04-x64-ruby-3.2.7-wd-/home/runner/work/puppet-dns/puppet-dns-with--without-development:test:release-only--v-1-Gemfile.lock-ebac66d6ee5ce40635c58c7257e9ae743717905930392928fee773f20c831f56, setup-ruby-bundler-cache-v6-ubuntu-20.04-x64-ruby-3.2.7-wd-/home/runner/work/puppet-dns/puppet-dns-with--without-development:test:release-only--v-1-Gemfile.lock-

Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists

The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101

Cache not found for keys: setup-ruby-bundler-cache-v6-ubuntu-20.04-x64-ruby-3.2.7-wd-/home/runner/work/puppet-dns/puppet-dns-with--without-development:test:release-only--v-1-Gemfile.lock-ebac66d6ee5ce40635c58c7257e9ae743717905930392928fee773f20c831f56, setup-ruby-bundler-cache-v6-ubuntu-20.04-x64-ruby-3.2.7-wd-/home/runner/work/puppet-dns/puppet-dns-with--without-development:test:release-only--v-1-Gemfile.lock-

Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists

The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101

Cache not found for keys: setup-ruby-bundler-cache-v6-ubuntu-20.04-x64-ruby-3.2.7-wd-/home/runner/work/puppet-dns/puppet-dns-with--without-development:test:release-only--v-1-Gemfile.lock-ebac66d6ee5ce40635c58c7257e9ae743717905930392928fee773f20c831f56, setup-ruby-bundler-cache-v6-ubuntu-20.04-x64-ruby-3.2.7-wd-/home/runner/work/puppet-dns/puppet-dns-with--without-development:test:release-only--v-1-Gemfile.lock-

Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists

The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101

Cache not found for keys: setup-ruby-bundler-cache-v6-ubuntu-20.04-x64-ruby-3.2.7-wd-/home/runner/work/puppet-dns/puppet-dns-with--without-development:test:release-only--v-1-Gemfile.lock-ebac66d6ee5ce40635c58c7257e9ae743717905930392928fee773f20c831f56, setup-ruby-bundler-cache-v6-ubuntu-20.04-x64-ruby-3.2.7-wd-/home/runner/work/puppet-dns/puppet-dns-with--without-development:test:release-only--v-1-Gemfile.lock-

Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists

The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101

Cache not found for keys: setup-ruby-bundler-cache-v6-ubuntu-20.04-x64-ruby-3.2.7-wd-/home/runner/work/puppet-dns/puppet-dns-with--without-development:test:release-only--v-1-Gemfile.lock-ebac66d6ee5ce40635c58c7257e9ae743717905930392928fee773f20c831f56, setup-ruby-bundler-cache-v6-ubuntu-20.04-x64-ruby-3.2.7-wd-/home/runner/work/puppet-dns/puppet-dns-with--without-development:test:release-only--v-1-Gemfile.lock-