-
Notifications
You must be signed in to change notification settings - Fork 39.8k
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
Cleanup orphan logging that goes on in the sync loop. #44938
Cleanup orphan logging that goes on in the sync loop. #44938
Conversation
part of general kubelet status / health improvements issue #45029 |
cc @kubernetes/sig-node-pr-reviews |
/lgtm /cc @kubernetes/sig-storage-pr-reviews, as this may affect the debuggability(?). |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jayunit100, yujuhong
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
@@ -107,18 +110,29 @@ func (kl *Kubelet) cleanupOrphanedPodDirs( | |||
// If there are still volume directories, do not delete directory | |||
volumePaths, err := kl.getPodVolumePathListFromDisk(uid) | |||
if err != nil { | |||
glog.Errorf("Orphaned pod %q found, but error %v occurred during reading volume dir from disk", uid, err) | |||
orphanVolumeErrors = append(orphanVolumeErrors, fmt.Errorf("Orphaned pod %q found, but error %v occurred during reading volume dir from disk", uid, err)) |
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.
@jayunit100 do you have any insight re: https://bugzilla.redhat.com/show_bug.cgi?id=1445410 -- i find it strange we hit times where err printed nil here ;-)
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.
i think a while back it also used to spam this if there were any volume paths floating around 041fa64#diff-79d1ea3801b52a2add9229183049f4c2
this is fixed now, so it might be lagging in some older forks/distros ., i doubt you will ever see <nil>
err running off of the current or any recent (4 months) master fork
@yujuhong why does it hate my release note? |
My guess is that you need to use the "```release-note" format |
/release-note |
Automatic merge from submit-queue (batch tested with PRs 45033, 44961, 45021, 45097, 44938) |
I still have this problem in version 1.7.8:
Which version will solve this? |
Still suffering from this in 1.8.5(-rancher1). |
What this PR does / why we need it:
Fixes #44937
Before this PR The older logs were like this:
The problem being that, all the volumes were spammed w/ no summary info.
After this PR the logs look like this:
And with logging turned up, the extra info logs are shown with details:
Release note