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

[ws-daemon] excessive logging for could not get resource information #12330

Closed
jenting opened this issue Aug 24, 2022 · 4 comments · Fixed by #14218
Closed

[ws-daemon] excessive logging for could not get resource information #12330

jenting opened this issue Aug 24, 2022 · 4 comments · Fixed by #14218
Assignees
@utam0k
Labels
component: ws-daemon team: workspace Issue belongs to the Workspace team type: bug Something isn't working

Comments

@jenting
Copy link
Contributor

jenting commented Aug 24, 2022 •
edited by kylos101
Loading

Bug description

From GCP log in us63, we see the could not get resource information error.

failed to get cpu usage:
    github.com/gitpod-io/gitpod/ws-daemon/pkg/iws.resolveCPUStatV2
        github.com/gitpod-io/gitpod/ws-daemon/pkg/iws/iws.go:1289
  - open /mnt/node-cgroups/kubepods.slice/kubepods-burstable.slice/kubepods-burstable-podad41d5dd_930e_446c_879f_7628dce993b6.slice/cri-containerd-12ada141db6a1d737640badc384fe73254d097910312ee32c400882bee1dd837.scope/cpu.stat: no such file or directory

Steps to reproduce

Dunno

Workspace affected

No response

Expected behavior

No response

Example repository

No response

Anything else?

No response

Definition of done

Log as a warning when its not an error. If its truly an error, log is as an error.
@jenting jenting added type: bug Something isn't working component: ws-daemon team: workspace Issue belongs to the Workspace team labels Aug 24, 2022
@utam0k
Copy link
Contributor

utam0k commented Aug 24, 2022

same question
#12329 (comment)

@utam0k utam0k closed this as not planned Won't fix, can't repro, duplicate, stale Aug 24, 2022
@utam0k utam0k moved this to Awaiting Deployment in 🌌 Workspace Team Aug 24, 2022
@utam0k utam0k removed the status in 🌌 Workspace Team Aug 24, 2022
@kylos101 kylos101 reopened this Oct 26, 2022
@kylos101
Copy link
Contributor

Reopening and adding to inbox because the frequency is consistent and rather noisy.

Logs

@kylos101
Copy link
Contributor

@Furisto @utam0k could I ask you to reevaluate this issue? Context.

@kylos101 kylos101 changed the title ws-daemon: could not get resource information [ws-daemon] excessive logging for could not get resource information Oct 26, 2022
@utam0k utam0k mentioned this issue Oct 27, 2022
Merged
4 tasks
@roboquat roboquat moved this to Awaiting Deployment in 🌌 Workspace Team Oct 27, 2022
@kylos101
Copy link
Contributor

@utam0k assigning you, as you fixed in a PR 👍

@jenting jenting moved this from Awaiting Deployment to In Validation in 🌌 Workspace Team Nov 4, 2022
@utam0k utam0k moved this from In Validation to Done in 🌌 Workspace Team Nov 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@utam0k utam0k

Labels
component: ws-daemon team: workspace Issue belongs to the Workspace team type: bug Something isn't working
Projects
No open projects
🌌 Workspace Team
Status: Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

IWS: Don't record the error log from getResourceInfo when the workspace has gone. gitpod-io/gitpod
3 participants
@kylos101 @utam0k @jenting