-
Notifications
You must be signed in to change notification settings - Fork 174
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 - should setup and maintain up to date TLS certificates #2096
Labels
kind/flake
Categorizes issue or PR as related to a flaky test.
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Comments
zimnx
added
kind/flake
Categorizes issue or PR as related to a flaky test.
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
labels
Aug 27, 2024
The Scylla Operator project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
/lifecycle stale |
scylla-operator-bot
bot
added
the
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
label
Sep 27, 2024
scylla-operator-bot
bot
removed
the
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
label
Oct 2, 2024
Merged
1 task
tnozicka
added
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
and removed
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
labels
Oct 22, 2024
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.
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Link to the job that flaked.
https://prow.scylla-operator.scylladb.com/view/gs/scylla-operator-prow/pr-logs/pull/scylladb_scylla-operator/2066/pull-scylla-operator-master-e2e-gke-parallel-clusterip/1828179211538403328
Snippet of what failed.
Looks like a cleanup Pod - triggered after considering ScyllaCluster as rolled out (it's an expected edge case) - got picked up by the test logic and IP of it (empty one) failed the assertion.
The text was updated successfully, but these errors were encountered: