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.

Sign up for GitHub

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

Jump to bottom

Bottlerocket 1.13.4 runc 1.1.6 excessive logging "Path does not exist" #3063

Closed
hajdukda opened this issue Apr 30, 2023 · 3 comments
Closed

Bottlerocket 1.13.4 runc 1.1.6 excessive logging "Path does not exist" #3063

hajdukda opened this issue Apr 30, 2023 · 3 comments
Labels
area/core Issues core to the OS (variant independent) status/in-progress This issue is currently being worked on type/bug Something isn't working

Comments

@hajdukda
Copy link

hajdukda commented Apr 30, 2023 •
edited
Loading

After an update to latest bottlerocket os version (automatic using update operator)

We have noticed our clusters suddenly started generating tens of gbs of excessive logs related to ""Path does not exist""

Seems the becaused by missing verbose level that was fixed here: kubernetes/kubernetes#112650

Related issue: kubernetes/kubernetes#112124

When do we expect a fix for that ? or is there a plan to revert to previous version of runc ?

There seem to also be a memory and CPU issue caused by the upgrade also.
@hajdukda hajdukda added status/needs-triage Pending triage or re-evaluation type/bug Something isn't working labels Apr 30, 2023
@hajdukda hajdukda changed the title Bottlerocket 1.13.4 runc 1.1.6 excessive logging "Path does not exist" [Regression] Bottlerocket 1.13.4 runc 1.1.6 excessive logging "Path does not exist" Apr 30, 2023
@hajdukda hajdukda changed the title [Regression] Bottlerocket 1.13.4 runc 1.1.6 excessive logging "Path does not exist" Bottlerocket 1.13.4 runc 1.1.6 excessive logging "Path does not exist" Apr 30, 2023
@stmcginnis
Copy link
Contributor

Hi @hajdukda - this update has already been reverted and a new release is in the works. I can't give an exact timeframe, but it should be "very soon".

@yeazelm
Copy link
Contributor

yeazelm commented May 1, 2023

I believe this is the same #3057 and as @stmcginnis stated, we are working on a new release to revert this change.

@arnaldo2792 arnaldo2792 added status/in-progress This issue is currently being worked on area/core Issues core to the OS (variant independent) and removed status/needs-triage Pending triage or re-evaluation labels May 1, 2023
@stmcginnis
Copy link
Contributor

This revert has been released, closing this issue.

@yeazelm yeazelm mentioned this issue Jun 2, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/core Issues core to the OS (variant independent) status/in-progress This issue is currently being worked on type/bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@stmcginnis @arnaldo2792 @yeazelm @hajdukda