scylla-operator has not updated status with observedGeneration for 10 minutes #2249
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.
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 hadobservedGeneration: 2
and some of the conditions were also only havingobservedGeneration: 2
. Yet from the test, byhttps://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 at12/11/24 09:09:22.869
and the collected status still containedobservedGeneration: 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
The text was updated successfully, but these errors were encountered: