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

CI: RuntimeDatapathMonitorTest With Sample Containers Cilium monitor verbose mode: ... is not in the output after timeout: 4m0s timeout expired #25178

Closed
christarazi opened this issue Apr 27, 2023 · 3 comments · Fixed by #25212
Closed

CI: RuntimeDatapathMonitorTest With Sample Containers Cilium monitor verbose mode: ... is not in the output after timeout: 4m0s timeout expired #25178

christarazi opened this issue Apr 27, 2023 · 3 comments · Fixed by #25212
Labels
area/CI Continuous Integration testing issue or flake ci/flake This is a known failure that occurs in the tree. Please investigate me!

Comments

@christarazi
Copy link
Member

Test Name

RuntimeDatapathMonitorTest With Sample Containers Cilium monitor verbose mode

Failure Output

"FROM 478 DEBUG:" is not in the output after timeout
Expected
    <*errors.errorString | 0xc000a29070>: {
        s: "FROM 478 DEBUG: is not in the output after timeout: 4m0s timeout expired",
    }
to be nil

Stack Trace

/home/jenkins/workspace/Cilium-PR-Runtime-net-next/runtime-gopath/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:515
"FROM 478 DEBUG:" is not in the output after timeout
Expected
    <*errors.errorString | 0xc000a29070>: {
        s: "FROM 478 DEBUG: is not in the output after timeout: 4m0s timeout expired",
    }
to be nil
/home/jenkins/workspace/Cilium-PR-Runtime-net-next/runtime-gopath/src/github.com/cilium/cilium/test/runtime/monitor.go:119

Standard Output

Number of "context deadline exceeded" in logs: 0
Number of "level=error" in logs: 0
Number of "level=warning" in logs: 0
Number of "Cilium API handler panicked" in logs: 0
Number of "Goroutine took lock for more than" in logs: 0
No errors/warnings found in logs

Standard Error

22:20:49 STEP: Running BeforeAll block for EntireTestsuite RuntimeDatapathMonitorTest
22:20:57 STEP: Running BeforeEach block for EntireTestsuite RuntimeDatapathMonitorTest
22:20:57 STEP: Setting PolicyEnforcement=default
22:20:57 STEP: Running BeforeAll block for EntireTestsuite RuntimeDatapathMonitorTest With Sample Containers
FAIL: "FROM 478 DEBUG:" is not in the output after timeout
Expected
    <*errors.errorString | 0xc000a29070>: {
        s: "FROM 478 DEBUG: is not in the output after timeout: 4m0s timeout expired",
    }
to be nil
=== Test Finished at 2023-04-27T22:25:19Z====
22:25:19 STEP: Running JustAfterEach block for EntireTestsuite RuntimeDatapathMonitorTest
===================== TEST FAILED =====================
22:25:19 STEP: Running AfterFailed block for EntireTestsuite RuntimeDatapathMonitorTest
cmd: sudo cilium endpoint list
Exitcode: 0 
Stdout:
 	 ENDPOINT   POLICY (ingress)   POLICY (egress)   IDENTITY   LABELS (source:key[=value])   IPv6                 IPv4            STATUS   
	            ENFORCEMENT        ENFORCEMENT                                                                                     
	 456        Disabled           Disabled          5779       container:id.httpd3           f00d::a0f:0:0:616b   10.15.127.3     ready   
	                                                            container:id.service1                                                      
	 478        Disabled           Disabled          6971       container:id.httpd1           f00d::a0f:0:0:f86f   10.15.228.244   ready   
	                                                            container:id.service1                                                      
	 530        Disabled           Disabled          1          reserved:host                                                      ready   
	 553        Disabled           Disabled          34545      container:id.httpd2           f00d::a0f:0:0:63be   10.15.239.133   ready   
	                                                            container:id.service1                                                      
	 679        Disabled           Disabled          36005      container:id.app1             f00d::a0f:0:0:67aa   10.15.48.65     ready   
	 1382       Disabled           Disabled          3868       container:id.app3             f00d::a0f:0:0:64bf   10.15.44.129    ready   
	 1430       Disabled           Disabled          6589       container:id.app2             f00d::a0f:0:0:2dcd   10.15.20.135    ready   
	 1467       Disabled           Disabled          4          reserved:health               f00d::a0f:0:0:f89f   10.15.230.174   ready   
	 
Stderr:
 	 

===================== Exiting AfterFailed =====================
22:25:22 STEP: Running AfterEach for block EntireTestsuite RuntimeDatapathMonitorTest With Sample Containers
22:25:22 STEP: Running AfterEach for block EntireTestsuite

Resources

Anything else?

No response
@christarazi christarazi added area/CI Continuous Integration testing issue or flake ci/flake This is a known failure that occurs in the tree. Please investigate me! labels Apr 27, 2023
@christarazi christarazi mentioned this issue Apr 27, 2023
Merged
@tklauser tklauser mentioned this issue Apr 28, 2023
Merged
@joestringer joestringer mentioned this issue Apr 28, 2023
Merged
@michi-covalent
Copy link
Contributor

hit this in #25179: https://jenkins.cilium.io/job/Cilium-PR-Runtime-net-next/6360/

@michi-covalent michi-covalent mentioned this issue Apr 28, 2023
Merged
@pchaigno
Copy link
Member

pchaigno commented Apr 29, 2023 •
edited

We should just remove this test IMO. It's testing our debug messages from datapath; that seems a bit excessive.

That said, this seems a bit suspect:
image

@michi-covalent michi-covalent mentioned this issue Apr 29, 2023
Merged
@michi-covalent
Copy link
Contributor

let's see if this gets approved or rejected: #25212

michi-covalent added a commit that referenced this issue Apr 30, 2023
@michi-covalent
Delete Cilium monitor verbose mode test
2700030 
Another option would be to quarantine the test and find an assignee to
make the test more robust, but I assert that we don't need test coverage
for monitor verbose output.

Fixes: #25178

Signed-off-by: Michi Mutsuzaki <michi@isovalent.com>
@brb brb mentioned this issue May 2, 2023
Merged
@meyskens meyskens mentioned this issue May 2, 2023
Merged
@lmb lmb mentioned this issue May 2, 2023
Merged
@mhofstetter mhofstetter mentioned this issue May 3, 2023
Merged
michi-covalent added a commit that referenced this issue May 4, 2023
@michi-covalent
Delete Cilium monitor verbose mode test
7335aa3 
Another option would be to quarantine the test and find an assignee to
make the test more robust, but I assert that we don't need test coverage
for monitor verbose output.

Fixes: #25178

Signed-off-by: Michi Mutsuzaki <michi@isovalent.com>
YutaroHayakawa pushed a commit to YutaroHayakawa/cilium that referenced this issue May 10, 2023
@michi-covalent @YutaroHayakawa
Delete Cilium monitor verbose mode test
9c109ff 
[ upstream commit 7335aa3 ]

Another option would be to quarantine the test and find an assignee to
make the test more robust, but I assert that we don't need test coverage
for monitor verbose output.

Fixes: cilium#25178

Signed-off-by: Michi Mutsuzaki <michi@isovalent.com>
Signed-off-by: Yutaro Hayakawa <yutaro.hayakawa@isovalent.com>
jrajahalme pushed a commit to jrajahalme/cilium that referenced this issue May 11, 2023
@michi-covalent @jrajahalme
Delete Cilium monitor verbose mode test
f484573 
[ upstream commit 7335aa3 ]

Another option would be to quarantine the test and find an assignee to
make the test more robust, but I assert that we don't need test coverage
for monitor verbose output.

Fixes: cilium#25178

Signed-off-by: Michi Mutsuzaki <michi@isovalent.com>
Signed-off-by: Jarno Rajahalme <jarno@isovalent.com>
jrajahalme pushed a commit that referenced this issue May 12, 2023
@michi-covalent @jrajahalme
Delete Cilium monitor verbose mode test
665be40 
[ upstream commit 7335aa3 ]

Another option would be to quarantine the test and find an assignee to
make the test more robust, but I assert that we don't need test coverage
for monitor verbose output.

Fixes: #25178

Signed-off-by: Michi Mutsuzaki <michi@isovalent.com>
Signed-off-by: Jarno Rajahalme <jarno@isovalent.com>
aanm pushed a commit that referenced this issue May 12, 2023
@michi-covalent @aanm
Delete Cilium monitor verbose mode test
4740437 
[ upstream commit 7335aa3 ]

Another option would be to quarantine the test and find an assignee to
make the test more robust, but I assert that we don't need test coverage
for monitor verbose output.

Fixes: #25178

Signed-off-by: Michi Mutsuzaki <michi@isovalent.com>
Signed-off-by: Yutaro Hayakawa <yutaro.hayakawa@isovalent.com>
YutaroHayakawa pushed a commit to YutaroHayakawa/cilium that referenced this issue May 15, 2023
@michi-covalent @YutaroHayakawa
Delete Cilium monitor verbose mode test
5606c1e 
[ upstream commit 7335aa3 ]

Another option would be to quarantine the test and find an assignee to
make the test more robust, but I assert that we don't need test coverage
for monitor verbose output.

Fixes: cilium#25178

Signed-off-by: Michi Mutsuzaki <michi@isovalent.com>
Signed-off-by: Yutaro Hayakawa <yutaro.hayakawa@isovalent.com>
aditighag pushed a commit that referenced this issue May 15, 2023
@michi-covalent @aditighag
Delete Cilium monitor verbose mode test
a93d7e4 
[ upstream commit 7335aa3 ]

Another option would be to quarantine the test and find an assignee to
make the test more robust, but I assert that we don't need test coverage
for monitor verbose output.

Fixes: #25178

Signed-off-by: Michi Mutsuzaki <michi@isovalent.com>
Signed-off-by: Yutaro Hayakawa <yutaro.hayakawa@isovalent.com>
jrajahalme pushed a commit to jrajahalme/cilium that referenced this issue May 22, 2023
@michi-covalent @jrajahalme
Delete Cilium monitor verbose mode test
08f7f4e 
[ upstream commit 7335aa3 ]

Another option would be to quarantine the test and find an assignee to
make the test more robust, but I assert that we don't need test coverage
for monitor verbose output.

Fixes: cilium#25178

Signed-off-by: Michi Mutsuzaki <michi@isovalent.com>
Signed-off-by: Yutaro Hayakawa <yutaro.hayakawa@isovalent.com>
Signed-off-by: Gilberto Bertin <jibi@cilium.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/CI Continuous Integration testing issue or flake ci/flake This is a known failure that occurs in the tree. Please investigate me!
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Delete "Cilium monitor verbose mode" test cilium/cilium
3 participants
@pchaigno @christarazi @michi-covalent