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

slo-monitor: the pulling image time of the pod is incorrectly recorded as 1970-01-01 00:00:00 +0000 UTC #2525

Open
zyuce opened this issue Jan 22, 2024 · 2 comments · May be fixed by #2527
Open
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@zyuce
Copy link

zyuce commented Jan 22, 2024

What happened:
The slo-monitor collects pod lifecycle time by watching events, but it incorrectly records the time of starting pulling image.
I0122 02:27:28.157857 1 pod_monitor.go:324] Observed Pod default/netshoot creation: created 2024-01-22 02:27:21 +0000 UTC, pulling: 1970-01-01 00:00:00 +0000 UTC, pulled: 2024-01-22 02:27:26 +0000 UTC, running: 2024-01-22 02:27:28.157849816 +0000 UTC m=+1186.391220756

What you expected to happen:
The time of pulling image is recorded correctly.

How to reproduce it (as minimally and precisely as possible):
Deploy the slo-monitor in k8s cluster with --v=5, create a common pod.
And then observe the log like above.

@zyuce zyuce added the kind/bug Categorizes issue or PR as related to a bug. label Jan 22, 2024
@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 Apr 21, 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 May 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
3 participants