RepoJournal
HashiCorp

@hashicorp

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

Pick a date

  1. Wed 20 may
  2. Thu 21 may
  3. Sat 23 may
  4. Sun 24 may
  5. Mon 25 may
  6. Tue 26 may
  7. Wed 27 may
  8. Thu 28 may
  9. Fri 29 may
  10. Sat 30 may
  11. Sun 31 may
  12. Mon 1 jun
  13. Mon 8 jun
  14. Tue 9 jun
  15. Wed 10 jun
  16. Thu 11 jun
  17. Fri 12 jun
  18. Sat 13 jun
  19. Sun 14 jun
  20. Mon 15 jun
  21. Tue 16 jun
  22. Wed 17 jun
  23. Thu 18 jun
  24. Fri 19 jun
  25. Sat 27 jun
  26. Sun 28 jun
  27. Tue 30 jun
  28. Wed 1 jul
  29. Thu 2 jul
  30. Today 3 jul

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.

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

FAQ

What changed 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.
What should HashiCorp teams do about it?
Review and test the server IP collision fix in your staging environment before deploying to production • Audit any recent server renames or maintenance operations for the symptoms described in the fix • Monitor Raft consensus health if running Consul at scale
Which HashiCorp repositories shipped on June 16, 2026?
hashicorp/consul, hashicorp/consul-esm, hashicorp/action-setup-bob

Related across the cluster

For your repos

The showcase is a teaser.
Your wire is the product.

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • •14 famous open source orgs
  • •One wire per day
  • •Public, generic
  • •Read on the web, when you remember

Your wire

  • →Up to 1,500 of your repos - orgs, deps, vendors
  • →Morning and evening briefs
  • →Action items routed to your team
  • →Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.