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
Ignore sysfs file read errors #799
Conversation
96b1970
to
0c0afad
Compare
0c0afad
to
1dbca66
Compare
we can set directpv/pkg/device/sysfs_linux.go Line 75 in c0ae169
|
@harshavardhana @Praveenrajmani Do you guys see |
yes @balamurugana portworx volumes are missing this |
Yes portworx devices seems to have it missing, an another CSI product. |
We can simply ignore all devices that do not comply with what we want. I am not big fan of failing pods with no easy to understand errors. Unless we want to log why we are ignoring the drives? That is okay too. |
@harshavardhana You could pass |
No @balamurugana that is not a complete fix. We should ignore all devices that do not comply with Disk metadata that we want. It is not just about The current PR simply addresses this more comprehensively. For example, portworx has a couple of other files missing as well. If we only fixed IMO we shouldn't crash our pods unnecessarily. We should work when we have other good drives we can manage. This is a support nightmare and also a bad POC experience. We should be able to deploy DirectPV without @balamurugana or @Praveenrajmani's involvement. |
1dbca66
to
bf9e1d9
Compare
bf9e1d9
to
76ac5aa
Compare
No description provided.