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

feat: setup volume health monitoring based on lv_attr bits #916

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

jakobmoellerdev
Copy link
Contributor

@jakobmoellerdev jakobmoellerdev commented May 15, 2024

fix #874

First implementation draft of using Volume Health Monitoring.

TODO:

Signed-off-by: Jakob Möller <jmoller@redhat.com>
Signed-off-by: Jakob Möller <jmoller@redhat.com>
Signed-off-by: Jakob Möller <jmoller@redhat.com>
@jakobmoellerdev
Copy link
Contributor Author

Im having trouble testing this in an artificial environment. Does someone here have an idea on how to enforce a failure state on one of the volumes?

@peng225
Copy link
Contributor

peng225 commented Jun 3, 2024

@jakobmoellerdev
Sorry for my late response. Are you still in trouble?

Does someone here have an idea on how to enforce a failure state on one of the volumes?

Do you mean that you want to have a PV (of Kubernetes) in failure status in test environment?

@jakobmoellerdev
Copy link
Contributor Author

Hi, yes im still stuck there and am looking for input. I am trying to get a lv into a state that would trigger the Volume Health Monitoring error without other errors such as mounting / deactivation to interfere so this can be properly tested

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In progress
Development

Successfully merging this pull request may close these issues.

RFE: Implementation of Volume Health Monitoring
2 participants