Fix ca-certificates duplicate declaration on elastic nodes#280
Merged
Conversation
profile::infrahouse_repo (included from profile::base, i.e. every node) ensure_packages'd ca-certificates. On elastic_master/elastic_data, profile::elastic::tls also declared Package['ca-certificates'] *natively*, so the catalog failed with a duplicate declaration (seen on sandbox elastic_master ip-10-0-2-191). Development never surfaced it because only the jumphost role was exercised there. ca-certificates is a fleet-wide TLS dependency, so let base own it: - Keep it in profile::infrahouse_repo's ensure_packages (single owner). - Drop the native package block from profile::elastic::tls; its file resources keep `require => Package['ca-certificates']`, which now resolves to the base-level declaration (stage-ordered before the elastic files). Behavior-preserving: both declared `ensure => present`. Applied to dev and sandbox; global picks it up with the Phase 3 promotion. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
infrahouse8
approved these changes
Jul 4, 2026
akuzminsky
added a commit
that referenced
this pull request
Jul 4, 2026
Move profile::infrahouse_repo (+ converge-infrahouse-keyring.sh) into the global modules/profile that production uses (no env-local override), and wire the include into profile::base. Bundle the elastic::tls ca-certificates fix in the same change so production's elastic nodes never see the duplicate-declaration state that briefly hit sandbox (see #280). All four touched files are now byte-identical across global/development/sandbox, restoring the module-parity invariant from #276. Validated in development (jumphost + from-zero instance) and sandbox (elastic_master + jumphost, via SSM): catalog compiles, keyring == published bundle, source list byte-identical to cloud-init's seed, apt-get update clean. Note: the live release-noble bundle is still single-key; this class readies the fleet but the rotation only completes once the upstream new key is published into the bundle (before 2026-07-20). Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Regression
profile::infrahouse_repo(added in #278/#279, included fromprofile::base→ every node)ensure_packages'dca-certificates. Onelastic_master/elastic_data,profile::elastic::tlsalso declaredPackage['ca-certificates']natively, so the catalog failed:Seen on sandbox
elastic_masterip-10-0-2-191. Development never surfaced it because only the jumphost role was exercised there.Fix
ca-certificatesis a fleet-wide TLS dependency, so letbaseown it:profile::infrahouse_repo'sensure_packages(single owner).package { 'ca-certificates' }block fromprofile::elastic::tls; its file resources keeprequire => Package['ca-certificates'], which now resolves to the base-level declaration (stage-ordered before the elastic files — strictly better ordering).Behavior-preserving — both were
ensure => present.curl/gnupgdon't collide (no native declarations;elastic::repousesgnupg2, a different title).Applied to dev + sandbox; global picks it up with the Phase 3 promotion.
🤖 Generated with Claude Code