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

Bacalhau connect / delete no ability to reconnect #4198

Open
aronchick opened this issue Jul 3, 2024 · 1 comment
Open

Bacalhau connect / delete no ability to reconnect #4198

aronchick opened this issue Jul 3, 2024 · 1 comment
Assignees
@wdbaruni
Labels
comp/node-manager Pertains to node management request/accepted Request: The issue has been reviewed and accepted for further action type/bug Type: Something is not working as expected
Milestone
v1.5.0

Comments

@aronchick
Copy link
Collaborator

Repro:

  • start a cluster
  • connect a compute node
  • stop the compute node
  • delete the node
  • restart the node

Expected

Node should be visible again

Actual

Node not available
@aronchick aronchick added type/bug Type: Something is not working as expected request/new Request: Indicates a new request that has been submitted and awaits initial triage labels Jul 3, 2024
@wdbaruni
Copy link
Member

This is an actual bug and related to how we persist the registration state in the compute node. We try to avoid having the compute node register each time during startup and skip if its local state says already registered, but this is wrong as the state can get out of sync, such as the scenario you mentioned.

Will cover this as part of #3861 by 1.5 or early 1.6

@wdbaruni wdbaruni self-assigned this Aug 11, 2024
@wdbaruni wdbaruni added request/accepted Request: The issue has been reviewed and accepted for further action and removed request/new Request: Indicates a new request that has been submitted and awaits initial triage labels Aug 11, 2024
@wdbaruni wdbaruni added this to the v1.5.0 milestone Aug 11, 2024
@wdbaruni wdbaruni added the comp/node-manager Pertains to node management label Oct 13, 2024 — with Linear
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@wdbaruni wdbaruni

Labels
comp/node-manager Pertains to node management request/accepted Request: The issue has been reviewed and accepted for further action type/bug Type: Something is not working as expected
Projects
Engineering Planning
Status: Next
Milestone
v1.5.0
Development

No branches or pull requests
2 participants
@aronchick @wdbaruni