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

Node status inaccurate and inconsistencies #394

Open
jgresham opened this issue Oct 30, 2023 · 0 comments
Open

Node status inaccurate and inconsistencies #394

jgresham opened this issue Oct 30, 2023 · 0 comments
Assignees
@jgresham
Labels
enhancement New feature or request

Comments

@jgresham
Copy link
Member

Feature details

Sometimes when a client crashes, the client is not accurately marked as stopped or error. Additionally, the node status does not change from "running" to an error or stopped state.

Currently node crashes are detected by subscribing to podman events however if sometimes the events are not parsed properly or podman chould crash. We should additionally run checks every so often to monitor the status of nodes.
@jgresham jgresham added the enhancement New feature or request label Oct 30, 2023
@jgresham jgresham self-assigned this Nov 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jgresham jgresham

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jgresham