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

Failure cluster [9339868f...] Containers Lifecycle should not launch second container before PostStart of the first container completed #120458

Closed
pacoxu opened this issue Sep 6, 2023 · 4 comments
Closed

Failure cluster [9339868f...] Containers Lifecycle should not launch second container before PostStart of the first container completed #120458

pacoxu opened this issue Sep 6, 2023 · 4 comments
Assignees
@gjkim42
Labels
kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. sig/node Categorizes an issue or PR as relevant to SIG Node. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
SIG Node CI/Test Board

Comments

@pacoxu
Copy link
Member

pacoxu commented Sep 6, 2023

Failure cluster 9339868fc1cf8e570508

Error text:
[FAILED] couldn't find that PostStart-regular-1 ever exited, got 2023-08-29 00:39:12 +0000 UTC 49.060000 regular-1 Starting
2023-08-29 00:39:12 +0000 UTC 49.070000 regular-1 Started
2023-08-29 00:39:12 +0000 UTC 49.070000 regular-1 Delaying
2023-08-29 00:39:14 +0000 UTC 50.970000 PostStart-regular-1 Starting
2023-08-29 00:39:14 +0000 UTC 50.980000 PostStart-regular-1 Started
2023-08-29 00:39:14 +0000 UTC 50.980000 PostStart-regular-1 Delaying
2023-08-29 00:39:14 +0000 UTC 51.070000 regular-1 Exiting
2023-08-29 00:39:14 +0000 UTC 51.430000 regular-2 Starting
2023-08-29 00:39:14 +0000 UTC 51.430000 regular-2 Started
2023-08-29 00:39:14 +0000 UTC 51.430000 regular-2 Delaying
2023-08-29 00:39:15 +0000 UTC 52.440000 regular-2 Exiting
In [It] at: test/e2e_node/container_lifecycle_test.go:377 @ 08/29/23 00:39:18.148

Recent failures:

2023/9/6 04:07:01 ci-crio-cgroupv1-node-e2e-conformance
2023/9/6 01:07:02 ci-crio-cgroupv1-node-e2e-conformance
2023/9/5 23:07:02 ci-crio-cgroupv1-node-e2e-conformance
2023/9/5 20:07:03 ci-crio-cgroupv1-node-e2e-conformance
2023/9/5 13:01:01 ci-crio-cgroupv1-node-e2e-conformance

/kind failing-test

/sig node
@k8s-ci-robot k8s-ci-robot added kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. sig/node Categorizes an issue or PR as relevant to SIG Node. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Sep 6, 2023
@gjkim42
Copy link
Member

gjkim42 commented Sep 6, 2023

/assign

@gjkim42
Copy link
Member

gjkim42 commented Sep 6, 2023

/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Sep 6, 2023
@gjkim42 gjkim42 mentioned this issue Sep 6, 2023
Merged
@SergeyKanzhelev SergeyKanzhelev moved this from Triage to Issues - In progress in SIG Node CI/Test Board Sep 6, 2023
@gjkim42
Copy link
Member

gjkim42 commented Sep 19, 2023

https://storage.googleapis.com/k8s-triage/index.html?test=should%20not%20launch%20second%20container%20before%20PostStart%20of%20the%20first%20container%20completed

I suppose this issue is addressed after #120464.

/close

@k8s-ci-robot
Copy link
Contributor

@gjkim42: Closing this issue.

In response to this:

https://storage.googleapis.com/k8s-triage/index.html?test=should%20not%20launch%20second%20container%20before%20PostStart%20of%20the%20first%20container%20completed

I suppose this issue is addressed after #120464.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

SIG Node CI/Test Board automation moved this from Issues - In progress to Done Sep 19, 2023
@Vyom-Yadav Vyom-Yadav mentioned this issue May 21, 2024
Closed
@collinm10 collinm10 mentioned this issue May 22, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gjkim42 gjkim42

Labels
kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. sig/node Categorizes an issue or PR as relevant to SIG Node. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
SIG Node CI/Test Board
Done
Milestone
No milestone
Development

No branches or pull requests
3 participants
@pacoxu @gjkim42 @k8s-ci-robot