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.

Sign up for GitHub

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

Jump to bottom

Primary election does not take place after primary VM is deleted #92

Open
JaydenLiang opened this issue Jan 25, 2022 · 0 comments · Fixed by #95
Open

Primary election does not take place after primary VM is deleted #92

JaydenLiang opened this issue Jan 25, 2022 · 0 comments · Fixed by #95
Labels
tracked internal issue that is tracked in an internal system. with "internal issue id:" in the desc.

Comments

@JaydenLiang
Copy link
Contributor

internal issue id: 0777245

Please follow the steps to reproduce the issue:

  1. Spawn a PAYG stack with new VPC
  2. Wait till stack is ready and primary is elected
  3. Delete the Primary from the Azure portal
  4. Wait for a new Instance to spawn.
  5. New Primary is never elected

Noticed the primary election entry in cosmos db is empty as well.

Waited for around 12 hours but a new primary is never elected.
@JaydenLiang JaydenLiang added the tracked internal issue that is tracked in an internal system. with "internal issue id:" in the desc. label Jan 25, 2022
This was referenced Jan 28, 2022
Merged
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
tracked internal issue that is tracked in an internal system. with "internal issue id:" in the desc.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Bugfix gh 92 election issue when primary vm deleted fortinet/fortigate-autoscale-azure
1 participant
@JaydenLiang