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

[Flake] RemoteKubernetesCluster [It] should run healthcheck probes and propagate results to status conditions #2303

Open
rzetelskik opened this issue Jan 7, 2025 · 2 comments
Labels
kind/flake Categorizes issue or PR as related to a flaky test. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@rzetelskik
Copy link
Member

Link to the job that flaked.

https://prow.scylla-operator.scylladb.com/view/gs/scylla-operator-prow/pr-logs/pull/scylladb_scylla-operator/2298/pull-scylla-operator-master-e2e-gke-parallel/1876652807881232384#1:test-build-log.txt%3A948

/priority important-soon
/kind flake

Snippet of what failed.

  [FAILED] Unexpected error:
      <*fmt.wrapError | 0xc0007b60a0>: 
      waiting has been interupted ([false]): timed out waiting for the condition
      {
          msg: "waiting has been interupted ([false]): timed out waiting for the condition",
          err: <wait.errInterrupted>{
              cause: <*errors.errorString | 0xc000133350>{
                  s: "timed out waiting for the condition",
              },
          },
      }
  occurred
  In [It] at: github.com/scylladb/scylla-operator/test/e2e/set/remotekubernetescluster/remotekubernetescluster_healthcheck.go:77 @ 01/07/25 15:57:26.805
@rzetelskik rzetelskik added the kind/flake Categorizes issue or PR as related to a flaky test. label Jan 7, 2025
@scylla-operator-bot scylla-operator-bot bot added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Jan 7, 2025
@rzetelskik
Copy link
Member Author

We suspect this is caused by the recent changes in CI infra. The operator is being overwhelmed with cert generation at first. It should be mitigated with giving operator a guaranteed QoS class and increasing the limits for cert generation.

@rzetelskik rzetelskik added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Jan 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/flake Categorizes issue or PR as related to a flaky test. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

No branches or pull requests

1 participant