RepoJournal
HashiCorp

@hashicorp

Terraform, Vault, Consul - infra-as-code for ops teams

Keep up with HashiCorp in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

One email a day. Unsubscribe in one click.

Pick a date

Topics: Go Infrastructure Full archive →

The Wire · Showcase

CONSUL SERVERS LOSE THEIR MINDS AFTER RENAME

By RepoJournal · Filed · About HashiCorp

A critical bug in Consul server rejoining after maintenance leaves clusters unable to find their Raft leader, breaking peer lookups and causing silent failures across production.

Consul shipped a fix [1] for a lurking incident where renaming and rejoining a server creates a phantom IP collision that breaks the entire Raft consensus layer. You'll see the error "Raft leader not found in server lookup mapping" followed by cascading 500s when the cluster can't locate its peers. This isn't theoretical, it's a known production issue that the team debugged after it happened to them. On the observability front, consul-esm rolled out test coverage reporting [2] across its CI pipeline, borrowing the working approach from consul-dataplane to catch regressions earlier. The team also landed a workaround for stale read node configuration [3] that was blocking their badge workflow, fixing a CI footgun where running coverage twice on the same branch would fail. Finally, action-setup-bob bumped its checkout action [4] to 6.0.3, a routine maintenance update across the HashiCorp GitHub Actions ecosystem.

One email a day. Unsubscribe in one click.

Action items

References

  1. [1] Fix server ip collision ↗ hashicorp/consul
  2. [2] ci: add Go test coverage reporting ↗ hashicorp/consul-esm
  3. [3] ci: decouple stale_read_nodes config fix into separate PR (#380) hashicorp/consul-esm
  4. [4] Bump actions/checkout from 6.0.2 to 6.0.3 ↗ hashicorp/action-setup-bob

Quick answers

What shipped in HashiCorp on June 16, 2026?
A critical bug in Consul server rejoining after maintenance leaves clusters unable to find their Raft leader, breaking peer lookups and causing silent failures across production. In total, 11 commits and 5 pull requests landed.
Who contributed to HashiCorp on June 16, 2026?
3 developers shipped this update, including anyasabo, Surabhi-1605, and dependabot[bot].
What were the notable HashiCorp updates?
Fix server ip collision, ci: add Go test coverage reporting, and ci: decouple stale_read_nodes config fix into separate PR (#380).

More from @hashicorp

Daily updates, in your inbox

Follow HashiCorp

Keep up with HashiCorp in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

One email a day. Unsubscribe in one click. Read a past issue →

Elsewhere on the wire

Want every project, not just this one?

We use privacy-friendly analytics (Google Analytics, IP-anonymized) to see which pages help readers. No ads, and we never sell your data. See our Privacy Policy.