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

scylla-operator has not updated status with observedGeneration for 10 minutes #2249

Open
tnozicka opened this issue Dec 11, 2024 · 0 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@tnozicka
Copy link
Member

tnozicka commented Dec 11, 2024

While investigating this e2e
https://prow.scylla-operator.scylladb.com/view/gs/scylla-operator-prow/pr-logs/pull/scylladb_scylla-operator/2212/pull-scylla-operator-master-e2e-gke-parallel/1866763303280185344#1:test-build-log.txt%3A2247
I noticed the cluster that "failed to rollout" had generation: 3 but the status had observedGeneration: 2 and some of the conditions were also only having observedGeneration: 2. Yet from the test, by
https://prow.scylla-operator.scylladb.com/view/gs/scylla-operator-prow/pr-logs/pull/scylladb_scylla-operator/2212/pull-scylla-operator-master-e2e-gke-parallel/1866763303280185344#1:test-build-log.txt%3A2154
2 updates have been applied to the ScyllaCluster meaning it's generation was 3 at that time (08:58:32.884). The test failed at 12/11/24 09:09:22.869 and the collected status still contained observedGeneration: 2.
https://gcsweb.scylla-operator.scylladb.com/gcs/scylla-operator-prow/pr-logs/pull/scylladb_scylla-operator/2212/pull-scylla-operator-master-e2e-gke-parallel/1866763303280185344/artifacts/e2e/cluster-0/namespaces/e2e-test-scyllacluster-cfwmn-0-wtjr7/scyllaclusters.scylla.scylladb.com/basic-hmvql.yaml

@tnozicka tnozicka added kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. 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