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

TestOOMControllerReporting fails for OLM tests #954

Open
czunker opened this issue Nov 23, 2023 · 0 comments
Open

TestOOMControllerReporting fails for OLM tests #954

czunker opened this issue Nov 23, 2023 · 0 comments
Labels
bug Something isn't working testing

Comments

@czunker
Copy link
Contributor

czunker commented Nov 23, 2023

Describe the bug

=== RUN   TestAuditConfigOOMSuite/TestOOMControllerReporting
2023-11-23T07:11:23.095+0100	INFO	integration/audit_config_base_suite.go:246	Create an audit config that enables nothing.
2023-11-23T07:11:25.114+0100	INFO	integration/audit_config_base_suite.go:269	Reducing memory limit to trigger OOM.
    audit_config_base_suite.go:277: 
        	Error Trace:	/home/christian/workspace/mondoo/github.com/mondoo-operator/tests/integration/audit_config_base_suite.go:277
        	            				/home/christian/workspace/mondoo/github.com/mondoo-operator/tests/integration/audit_config_oom_test.go:20
        	Error:      	Received unexpected error:
        	            	test did not succeed after 100 retries
        	Test:       	TestAuditConfigOOMSuite/TestOOMControllerReporting
        	Messages:   	Failed to find degraded condition
2023-11-23T07:14:45.620+0100	INFO	installer/installer.go:186	gathering all logs from the test
2023-11-23T07:14:45.620+0100	INFO	utils/k8s_helper.go:256	Gathering logs for all pods in namespace mondoo-operator

https://github.com/mondoohq/mondoo-operator/actions/runs/6961336325/job/18954848713

To Reproduce
Steps to reproduce the behavior:

  1. Install operator via OLM
  2. Run integration tests
  3. Note the error

Expected behavior
Tests should pass.

Additional context
Most works as usual, but the changed resource settings aren't applied to the Pod:

k -n mondoo-operator get all
NAME                                                                  READY   STATUS      RESTARTS   AGE
pod/68191bded91e8d8ceaea900c8078dfdb90eb2ff11698389c4489741f8axtqlv   0/1     Completed   0          6m55s
pod/ghcr-io-mondoohq-mondoo-operator-bundle-v1-18-0                   1/1     Running     0          7m6s
pod/mondoo-operator-controller-manager-f4b477475-7dj75                1/1     Running     0          6m41s

NAME                                                         TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)    AGE
service/mondoo-operator-controller-manager-metrics-service   ClusterIP   10.111.249.127   <none>        8080/TCP   6m43s

NAME                                                 READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/mondoo-operator-controller-manager   1/1     1            1           6m41s

NAME                                                           DESIRED   CURRENT   READY   AGE
replicaset.apps/mondoo-operator-controller-manager-57f5c455c   0         0         0       4m52s
replicaset.apps/mondoo-operator-controller-manager-f4b477475   1         1         1       6m41s

NAME                                                                        COMPLETIONS   DURATION   AGE
job.batch/68191bded91e8d8ceaea900c8078dfdb90eb2ff11698389c4489741f8af7922   1/1           7s         6m55s

A new ReplicaSet is created, but the Pod is not replaced.

@czunker czunker added bug Something isn't working testing labels Nov 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working testing
Projects
None yet
Development

No branches or pull requests

1 participant