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

[BUG] [Remote State] During construction of valid chain we skip valid cluster UUIDs if the are previousClusterUUIDs for invalid UUIDs #10911

Closed
linuxpi opened this issue Oct 25, 2023 · 1 comment
Assignees
Labels
bug Something isn't working untriaged

Comments

@linuxpi
Copy link
Collaborator

linuxpi commented Oct 25, 2023

Describe the bug
During construction of valid chain we skip valid cluster UUIDs if the are previousClusterUUIDs for invalid UUIDs

To Reproduce
Steps to reproduce the behavior:

  1. Create a single node cluster.
  2. UUID1 is committed to remote
  3. Replace the node
  4. UUID2 is formed and committed. previousClusterUUID is UUID1
  5. Replace the node again.
  6. UUID3 is formed and published. previousClusterUUID is UUID2
  7. Before committing the UUID3 in remote(precommit), replace the node again
  8. The new nodes comes up, it will not consider any of the uuids in remote as valid.

Expected behavior
Chaining logic should not discard any valid cluster UUIDs which can be start of the final valid chain.

@linuxpi linuxpi added bug Something isn't working untriaged labels Oct 25, 2023
@soosinha
Copy link
Member

I am working on this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working untriaged
Projects
None yet
Development

No branches or pull requests

3 participants