Analyze Windows node logs and issues in must-gather data
Analyzes Windows node logs from must-gather data to identify common OpenShift Windows issues.
/plugin marketplace add openshift-eng/ai-helpers/plugin install must-gather@ai-helpers[must-gather-path] [--component COMPONENT]must-gather:windows
/must-gather:windows [must-gather-path] [--component COMPONENT] [--errors-only]
The must-gather:windows command analyzes Windows-specific logs collected during must-gather from Windows nodes in OpenShift clusters. It parses logs from Windows-specific components and identifies common Windows node issues.
This command analyzes logs from:
Use this command when:
Windows Node Logs Collection:
Windows node logs must be collected during must-gather. This requires:
kubernetes.io/os=windows)Expected Directory Structure:
must-gather/
└── host_service_logs/
└── windows/
└── log_files/
├── kube-proxy/kube-proxy.log
├── hybrid-overlay/hybrid-overlay.log
├── kubelet/kubelet.log
├── containerd/containerd.log
├── wicd/
│ ├── windows-instance-config-daemon.exe.INFO
│ ├── windows-instance-config-daemon.exe.ERROR
│ └── windows-instance-config-daemon.exe.WARNING
└── csi-proxy/csi-proxy.log
Locate Windows logs:
host_service_logs/windows/log_files/ directoryRun Windows log analyzer:
python3 plugins/must-gather/skills/must-gather-analyzer/scripts/analyze_windows_logs.py \
<must-gather-path>
Parse logs for errors and warnings:
Detect common Windows issues:
Generate report with:
The command outputs:
================================================================================
WINDOWS NODE LOGS ANALYSIS
================================================================================
Log directory: <path>
Components analyzed: 6/8
Total log lines: 125,432
Total errors found: 23
Total warnings: 15
COMPONENT STATUS:
COMPONENT LINES ERRORS WARNINGS STATUS
--------------------------------------------------------------------------------
kube-proxy 15,234 0 2 ✅ OK
hybrid-overlay 8,912 5 3 ❌ ERRORS
kubelet 45,123 12 5 ❌ ERRORS
containerd 32,456 6 4 ❌ ERRORS
wicd-info 12,345 0 1 ✅ OK
wicd-error 234 0 0 ✅ OK
wicd-warning 456 0 0 ✅ OK
csi-proxy 10,672 0 0 ✅ OK
================================================================================
DETECTED ISSUES
================================================================================
1. [CRITICAL] HNS (Host Network Service) Failures Detected
Found 5 HNS-related errors. This typically causes pods to fail in ContainerCreating state.
→ Check Windows node networking configuration. May need to restart HNS service or reboot node.
2. [CRITICAL] Container Runtime Failures
Found 6 containerd errors. Containers may fail to start.
→ Check containerd service status on Windows node. Review container image compatibility.
================================================================================
DETAILED ERRORS BY CATEGORY
================================================================================
HNS ERRORS (5):
--------------------------------------------------------------------------------
[hybrid-overlay:1234] failed to create HNS endpoint for pod default/test-pod
[hybrid-overlay:2345] HNS network attach failed: endpoint not found
...
CONTAINERD ERRORS (6):
--------------------------------------------------------------------------------
[containerd:567] failed to start container: runtime error
[kubelet:890] failed to create pod sandbox: containerd timeout
...
Analyze all Windows logs:
/must-gather:windows ./must-gather.local.123456789
Analyzes all Windows component logs and provides comprehensive report.
Analyze specific component:
/must-gather:windows ./must-gather.local.123456789 --component kubelet
Analyzes only kubelet logs from Windows nodes.
Summary only (skip detailed errors):
/must-gather:windows ./must-gather.local.123456789 --errors-only
Shows component status and detected issues without detailed error listing.
Analyze hybrid-overlay networking:
/must-gather:windows ./must-gather.local.123456789 --component hybrid-overlay
Focuses on hybrid-overlay logs to troubleshoot Linux-Windows pod connectivity.
Analyze containerd runtime:
/must-gather:windows ./must-gather.local.123456789 --component containerd
Reviews container runtime logs for Windows container failures.
Symptoms:
ContainerCreatingfailed to create HNS endpoint errorsRecommendations:
Restart-Service hnsSymptoms:
runtime error messagesRecommendations:
Symptoms:
Recommendations:
Symptoms:
Recommendations:
Symptoms:
Recommendations:
kubernetes.io/os=windowsgather_windows_nodes script in the must-gather collection phase--max-errors to adjust/must-gather:analyze for full cluster analysis including Windows resources