-
Notifications
You must be signed in to change notification settings - Fork 266
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
Not possible to read calico/felix logs in rke2/windows #4411
Milestone
Comments
This was referenced Jul 5, 2023
Validated on master branch using commit id 33caf61Environment DetailsInfrastructure Node(s) CPU architecture, OS, and Version: Cluster Configuration: Config.yaml:
Validation steps
Validation results:Ubuntu node
Windows node
ssh to windows node or login using RDP client and check for logs on the windows node
Validated log file is removed after uninstall
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environmental Info:
RKE2 Version:
Node(s) CPU architecture, OS, and Version:
OS: Windows
Cluster Configuration:
Any server Linux and at least one windows agent
Describe the bug:
The current code is not providing a meaningful way of checking the output of the calico or felix executing when doing rke2-windows with calico cni plugin. The code uses:
however, that does not work and in the rke2 service logs, we see nothing. In any case, that would be a non-ideal solution because those logs can be verbose. It is best if we had them in one file. According to calico, that should happen by default or can be configured with env vars (e.g. FELIX_LOGFILEPATH). However, it is not working in Windows
Steps To Reproduce:
Deploy a windows node and try to find
felix.log
, it does not exist. Also check the logs of the rke2 service and there is nothing related to calico or felixExpected behavior:
Be able to read logs in order to debug in case problems arise
Actual behavior:
Impossible to know what is going on
Additional context / logs:
The text was updated successfully, but these errors were encountered: