Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Creating new configuration entries are not forwarded to the primary datacenter #6327

Closed
mkeeler opened this issue Aug 15, 2019 · 0 comments
Closed
Labels
type/bug Feature does not function as expected
Milestone

Comments

@mkeeler
Copy link
Member

mkeeler commented Aug 15, 2019

Overview of the Issue

Neither the HTTP nor RPC APIs for applying a config entry will rewrite the target datacenter to send it to the configured primary datacenter. If they are applied in secondary dcs then this will lead to inconsistent state between datacenters as well as eventual removal as the config entry replication will see them as having been deleted in the primary.

Reproduction Steps

Steps to reproduce this issue, eg:

  1. Create two datacenter cluster
  2. `consul config write config.hcl
@mkeeler mkeeler added the type/bug Feature does not function as expected label Aug 15, 2019
@mkeeler mkeeler added this to the 1.6.0-final milestone Aug 15, 2019
@mkeeler mkeeler closed this as completed Aug 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Feature does not function as expected
Projects
None yet
Development

No branches or pull requests

1 participant