-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Improve "Waiting for Node volumes to be detached" log message #11108
Comments
/triage accepted |
/help |
@sbueringer: GuidelinesPlease ensure that the issue body includes answers to the following questions:
For more details on the requirements of such an issue, please see here and ensure that they are met. If this request no longer meets these requirements, the label can be removed In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
I'd take this task. |
Thx. I think we need some real life data to figure out what we can put in the logs |
Follow-up to: #11074 (comment)
This issue is about improving the "Waiting for Node volumes to be detached" log message added in #11074.
Open questions:
a) should we add details about the volumes that we are still waiting for?
b) which information about the volumes should be added to the logs (e.g. are the AttachedVolume.name fields useful to users?)
c) Should we add something to the condition?
Context:
The text was updated successfully, but these errors were encountered: