hashicorp / hashicorp/consul

raft: not part of stable configuration

Open
#9,716 0 comments 0 reactions 0 assignees View on GitHub
needs-investigation theme/internals theme/ipv6 type/bug type/question
Dominant language
Go
Stars
30.1k
Forks
4.6k
Avg merge
2d 6h
Merged PRs (30d)
43

Description

version: 1.6.10

We've tried to recover the cluster with peers.json according to:
https://support.hashicorp.com/hc/en-us/articles/115015603408-Consul-Errors-And-Warnings
But It didn't work.

Looking into the code where "raft: not part of stable configuration" raises, we found it may complain about the mismatch of ID in the data-dir/raft/snapshots/8-1137348-1612528070111/meta.json:

Configuration
`":{"Servers":[{"Suffrage":0,"ID":"[2001:db8:0003::1]:1110".........}]}`

We then manually replaced the ipv6 in the meta.json with its short form "2001:db8:3::1" and restarted the cluster. and everything goes fine!

It looks like the consul can not handle the meta.json correctly in ipv6 scenario.
please help confirm it, and suggest how to recover with peers.json in this case. we tried feed the consul with peers.json having 2001:db8:3::1 in it, but no luck, looks like the meta.json can not be overriden with peers.json

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.