-
Notifications
You must be signed in to change notification settings - Fork 6
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
Hs 312/sas device not found #53
Hs 312/sas device not found #53
Conversation
Upgrade to klogv2 for compatibility with libraries using klogv2 such as csi-lib-sas and for future-proofing
Occasionally previously removed devices which have not yet been removed from the array can be rediscovered by a rapid subsequent NodePublishVolume. To alleviate this for now, maintain a list of previously deleted devices and remove them.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some minor comments, but overall looks good.
go.mod
Outdated
@@ -37,7 +37,7 @@ require ( | |||
google.golang.org/protobuf v1.28.1 // indirect | |||
gopkg.in/tomb.v1 v1.0.0-20141024135613-dd632973f1e7 // indirect | |||
gopkg.in/yaml.v2 v2.4.0 // indirect | |||
k8s.io/klog/v2 v2.70.0 // indirect | |||
k8s.io/klog v1.0.0 // indirect |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This leads me to think that we are still using klog v1 somewhere, or is that related to klog v2 having a relationship with klog v1?
To mitigate possibility of a device that is in the process of being removed from being re-discovered by a subsequent NodePublishVolume call, maintain a list of previously removed devices and search for / re-remove them during publishing