Repository navigation
WINC-2046: Adds log file to windows-exporter - #4355
Conversation
|
Skipping CI for Draft Pull Request. |
|
Important Review skippedAuto reviews are limited based on label configuration. 🚫 Excluded labels (none allowed) (2)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Enterprise Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (4)
Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review. 📝 WalkthroughWalkthrough
Suggested reviewers: 🚥 Pre-merge checks | ✅ 20✅ Passed checks (20 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
@wgahnagl for the e2e test, ensure the resulting log file is captured in the artifacts, for example |
|
after this merge, need to update the must-gather collection script to include the new file in https://github.com/openshift/must-gather/blob/main/collection-scripts/gather_windows_node_logs#L11 @wgahnagl create a follow-up task/story for this. |
|
@wgahnagl: This pull request references WINC-2046 which is a valid jira issue. DetailsIn 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 openshift-eng/jira-lifecycle-plugin repository. |
jrvaldes
left a comment
There was a problem hiding this comment.
thanks for pushing the commit with tests, PTAL at the comments
8e17d00 to
42c196d
Compare
windows-exporter was not ommitting logs to a log file. This creates the log file and adds a unit test for the logs.
|
/test unit |
|
/test lint |
|
/test gcp-e2e-operator |
|
@coderabbitai full review |
|
azure-e2e-upgrade failed with: which is expected as the log file does not exist in prev version, and we are testing with a newer test suite. I lean towards skipping this test. @mansikulkarni96 WDYT? |
|
/override "Red Hat Konflux / windows-machine-config-operator-release-5-0-ec / windows-machine-config-operator-release-5-0" |
|
@jrvaldes: Overrode contexts on behalf of jrvaldes: Red Hat Konflux / windows-machine-config-operator-release-5-0-ec / windows-machine-config-operator-release-5-0 DetailsIn 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. |
|
/override ci/prow/gcp-e2e-operator failure not related, there good CI coverage in other jobs |
|
@jrvaldes: Overrode contexts on behalf of jrvaldes: ci/prow/gcp-e2e-operator DetailsIn 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. |
| "containerd/containerd.log", | ||
| "wicd/windows-instance-config-daemon.exe.INFO", | ||
| "csi-proxy/csi-proxy.log", | ||
| "windows_exporter/windows_exporter.log", |
There was a problem hiding this comment.
The azure-e2e-upgrade failure is caused by version skew: the new e2e test code expects windows_exporter/windows_exporter.log, but the upgrade job initially provisions Windows nodes with the previous WMCO version, which does not create that file. the log file is correctly created on fresh installs and after full reconciliation.
@wgahnagl explore the option to skip the windows_exporter.log expectation only in upgrade tests, not the whole Node Logs test. Add a new commit to make the new log check conditional on the node being configured by the current WMCO version, so fresh-install tests continue to enforce it.
There was a problem hiding this comment.
consider bringing this back ced41e5#diff-2a3ec15f2cd9038bbb6ad1be37818927fb913fd7a7ebd7cbb29ab41aeac4c3f7R25
`optionalLogs := []string{
"windows_exporter/windows_exporter.log",
}
@wgahnagl please move the PR back to draft, and push the fix for this, then test the azure-e2e-upgrade. |
|
/retest-required |
|
/hold cancel |
|
/lgtm |
|
/override "Red Hat Konflux / windows-machine-config-operator-release-5-0-ec / windows-machine-config-operator-release-5-0" |
|
@jrvaldes: Overrode contexts on behalf of jrvaldes: Red Hat Konflux / windows-machine-config-operator-release-5-0-ec / windows-machine-config-operator-release-5-0 DetailsIn 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. |
|
/override "ci/prow/vsphere-disconnected-e2e-operator" |
|
@jrvaldes: Overrode contexts on behalf of jrvaldes: ci/prow/vsphere-disconnected-e2e-operator DetailsIn 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. |
|
@wgahnagl: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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 understand the commands that are listed here. |
caa0b00
into
openshift:master
|
@jrvaldes: new pull request created: #4507 DetailsIn 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. |
|
/cherry-pick release-4.23 |
|
@jrvaldes: new pull request created: #4522 DetailsIn 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. |
This allows windows-exporter to use a log file, and use the globally configurable log files.
Summary by CodeRabbit
New Features
Bug Fixes