Skip to content
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

Flooded with WARN and INFO level logs #7071

Open
ivankatliarchuk opened this issue Jul 19, 2024 · 3 comments · May be fixed by #7179
Open

Flooded with WARN and INFO level logs #7071

ivankatliarchuk opened this issue Jul 19, 2024 · 3 comments · May be fixed by #7179
Labels
area/cluster-autoscaler kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@ivankatliarchuk
Copy link

Which component are you using?:

  • cluster-autoscaler 1.28.2
  • aws eks 1.28

Is your feature request designed to solve a problem? If so describe the problem this feature should solve.:

Du not flood logs with warning messages like.

  • Failed to check cloud provider .*. Issue closed
  • No node group for node .*. What this warning is trying to say?
  • Nodegroup is nil .*. How to action on this warning?
  • Start refreshing cloud .* as there is corresponding Refresh cloud provider node instances cache finished, refresh took or error message

Describe the solution you'd like.:

  • Revisit current logic as it could be outdated
  • Provide Q/A section how to fix this warning

Describe any alternative solutions you've considered.:

  • Configure these messages to be logged at the DEBUG level instead of WARN or INFO.

Additional context.:

Refresh start and successful refresh messages
Screenshot 2024-07-19 at 05 27 46

log patterns
Screenshot 2024-07-18 at 20 41 40

@ivankatliarchuk ivankatliarchuk added the kind/feature Categorizes issue or PR as related to a new feature. label Jul 19, 2024
@ivankatliarchuk ivankatliarchuk changed the title Flooded with warm level logs Flooded with WARN level logs Jul 19, 2024
@adrianmoisey
Copy link
Member

/area cluster-autoscaler

@ivankatliarchuk ivankatliarchuk changed the title Flooded with WARN level logs Flooded with WARN and INFO level logs Aug 17, 2024
@ivankatliarchuk ivankatliarchuk linked a pull request Aug 17, 2024 that will close this issue
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 15, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Dec 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/cluster-autoscaler kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants