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

workflows: Add --timestamps to kubectl logs #366

Merged
merged 1 commit into from
Jun 25, 2021

Conversation

gandro
Copy link
Member

@gandro gandro commented Jun 24, 2021

Timestamps are very useful when investigating a unknown CI failure. An
example where timestamps would yield us more information is for example
when a job runs into a timeout, such as e.g.
https://github.com/cilium/cilium-cli/runs/2904654177 where we suspect
that it might have run a bit longer than usual, but it's hard to tell.

Signed-off-by: Sebastian Wicki [email protected]

@gandro gandro requested review from a team as code owners June 24, 2021 13:29
@gandro gandro requested a review from nebril June 24, 2021 13:29
@gandro gandro requested a review from pchaigno June 24, 2021 13:29
@gandro gandro temporarily deployed to ci June 24, 2021 13:29 Inactive
Copy link
Member

@pchaigno pchaigno left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

@pchaigno pchaigno added ready-to-merge This PR has passed all tests and received consensus from code owners to merge. and removed ready-to-merge This PR has passed all tests and received consensus from code owners to merge. labels Jun 24, 2021
@tklauser tklauser removed the request for review from nebril June 24, 2021 14:20
@tklauser
Copy link
Member

The external workloads failure is a known flake: #329.

@gandro
Copy link
Member Author

gandro commented Jun 24, 2021

EKS seems to have hit a new flake: #367

@gandro
Copy link
Member Author

gandro commented Jun 24, 2021

Kind also seems to have hit a variant of flake #367. https://github.com/cilium/cilium-cli/pull/366/checks?check_run_id=2905226507

In both cases, we see UDP response packets for the DNS request, but no outgoing TCP connection. Because we don't collect L7 logs, it's not clear what the DNS request was.

Timestamps are very useful when investigating a unknown CI failure. An
example where timestamps would yield us more information is for example
when a job runs into a timeout, such as e.g.
https://github.com/cilium/cilium-cli/runs/2904654177 where we suspect
that it might have run a bit longer than usual, but it's hard to tell.

Signed-off-by: Sebastian Wicki <[email protected]>
@tklauser tklauser force-pushed the pr/gandro/add-timestamps-to-collected-logs branch from 18d5cff to fe21ed5 Compare June 25, 2021 09:51
@tklauser tklauser temporarily deployed to ci June 25, 2021 09:51 Inactive
@tklauser
Copy link
Member

Rebased to pick up c171080 hopefully helping to avoid some flakes.

@tklauser
Copy link
Member

tklauser commented Jun 25, 2021

The Kind failure looks like another instance of #367.

Given that this is the only failure now, I'm merging this as is - it will help us to debug other flakes.

@tklauser tklauser added the ready-to-merge This PR has passed all tests and received consensus from code owners to merge. label Jun 25, 2021
@tklauser tklauser merged commit d8bfe02 into master Jun 25, 2021
@tklauser tklauser deleted the pr/gandro/add-timestamps-to-collected-logs branch June 25, 2021 10:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready-to-merge This PR has passed all tests and received consensus from code owners to merge.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants