-
Notifications
You must be signed in to change notification settings - Fork 36
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
Backup task scheduling regression in 3.3.1: create backup target: create units: no keyspace matched criteria
#3989
Comments
@Strasznik would you be able to try 3.3.1 with Operator 1.13 for any backup-related jobs in SCT? |
@rzetelskik I ran some simple SCT test which is doing backup and it worked. Operator: scylla-operator:1.13.0
|
@Strasznik can you share the cluster spec as well? @Michal-Leszczynski suspects it only applies to single-node clusters. |
We need to move to 6.1 and 2024.1.7 (and .8 soon) |
@rzetelskik SCT tests are using KinD. Here is the spec:
|
Sorry for such a late response. The root cause of this issue connected to e449212. Previously SM also checked for the "system" prefix, but it was lost in the refactor done in e449212 and we don't run tests on a single node cluster, so that's why it didn't happen before - although the main issue is with assuming replication strategy. I will try to look for this information in Scylla API and fix this issue. |
…Scylla Validated manually as we don't have a single node test setup. Fixes #3989
…Scylla Validated manually as we don't have a single node test setup. Fixes #3989
…Scylla Validated manually as we don't have a single node test setup. Fixes #3989
This tmp commit job is to validate that the fix from scylladb/scylla-manager#4000 indeed fixes the 3.3.1 SM regression reported in scylladb/scylla-manager#3989.
This tmp commit job is to validate that the fix from scylladb/scylla-manager#4000 indeed fixes the 3.3.1 SM regression reported in scylladb/scylla-manager#3989.
…Scylla Validated manually as we don't have a single node test setup. Fixes #3989
…Scylla Validated manually as we don't have a single node test setup. Fixes #3989
There seems to be a regression in backup task scheduling in 3.3.1 release, as updating the ScyllaDB Manager and ScyllaDB Manager Agent versions to 3.3.1 in Scylla Operator's test suite breaks all the backup-related tests.
Here's an example run: https://prow.scylla-operator.scylladb.com/view/gs/scylla-operator-prow/pr-logs/pull/scylladb_scylla-operator/2089/pull-scylla-operator-master-e2e-gke-parallel/1825980285708144641#1:test-build-log.txt%3A1617
ScyllaCluster status snippet:
https://gcsweb.scylla-operator.scylladb.com/gcs/scylla-operator-prow/pr-logs/pull/scylladb_scylla-operator/2089/pull-scylla-operator-master-e2e-gke-parallel/1825980285708144641/artifacts/e2e/namespaces/e2e-test-scyllacluster-m4t6m-0-kf9mw/scyllaclusters.scylla.scylladb.com/basic-tpz79.yaml
ScyllaDB Manager logs snippet:
https://gcsweb.scylla-operator.scylladb.com/gcs/scylla-operator-prow/pr-logs/pull/scylladb_scylla-operator/2089/pull-scylla-operator-master-e2e-gke-parallel/1825980285708144641/artifacts/must-gather/0/namespaces/scylla-manager/pods/scylla-manager-79cf8b8677-hq7gk/scylla-manager.current
ScyllaDB Manager Agent logs: https://gcsweb.scylla-operator.scylladb.com/gcs/scylla-operator-prow/pr-logs/pull/scylladb_scylla-operator/2089/pull-scylla-operator-master-e2e-gke-parallel/1825980285708144641/artifacts/e2e/namespaces/e2e-test-scyllacluster-m4t6m-0-kf9mw/pods/basic-tpz79-us-east-1-us-east-1a-0/scylla-manager-agent.current
All artifacts: https://gcsweb.scylla-operator.scylladb.com/gcs/scylla-operator-prow/pr-logs/pull/scylladb_scylla-operator/2089/pull-scylla-operator-master-e2e-gke-parallel/1825980285708144641/artifacts/
All of our tests seem to be failing with create backup target: create units: no keyspace matched criteria error, which wasn't the case with earlier releases.
ScyllaDB Manager version: 3.3.1
ScyllaDB version: tested OS 6.0.1, 6.1.0 and Enterprise 2024.1.5, 2024.1.7
ScyllaDB Manager client version: tested 3.2.8 and 3.3.1
Xref: scylladb/scylla-operator#2089 (comment)
The text was updated successfully, but these errors were encountered: