Open fruch opened 1 month ago
Keep in mind this is upgrade from 6.0 -> master
so tablets is enabled to begin with, and all of the feature which are not supported would need to be disabled, otherwise this test can't run.
@bhalevy maybe it's not 6.0 issue, but 6.0.1, but please assign it.
@ShlomiBalalis please look into this issue
@bhalevy @ShlomiBalalis
this is the 2nd week, that all of the rolling upgrades tests are failing on this one
@fruch , can a solution be something like: if self.version_cdc_support():
-> if self.version_cdc_support() and not tablets_enabled:
@fruch , can a solution be something like:
if self.version_cdc_support():
->if self.version_cdc_support() and not tablets_enabled:
maybe, other option put this logic inside version_cdc_support()
either review it ontop of a PR, when seeing tests working with it, would be a bit easier
@yarongilor
seems like some part of it might be in: https://github.com/scylladb/scylla-cluster-tests/pull/7525
please sync with @aleksbykov
@fruch / @aleksbykov is this issue still relevant?
Packages
Scylla version:
6.0.0-20240606.a77615adf324
with build-id6c03ff0a571ac30073b739e9ba917545fe23e5c5
Kernel Version:5.15.0-1060-gcp
Issue description
Impact
User can't upgrade to master version, if he uses CDC
How frequently does it reproduce?
happened on all weekly upgrades tests
Installation details
Cluster size: 4 nodes (n2-highmem-64)
Scylla Nodes used in this run:
OS / Image:
https://www.googleapis.com/compute/v1/projects/ubuntu-os-cloud/global/images/family/ubuntu-2004-lts
(gce: undefined_region)Test:
rolling-upgrade-ubuntu20.04-test
Test id:050050a0-8ff6-4411-86e6-09f4900333bc
Test name:scylla-master/rolling-upgrade/rolling-upgrade-ubuntu20.04-test
Test config file(s):Logs and commands
- Restore Monitor Stack command: `$ hydra investigate show-monitor 050050a0-8ff6-4411-86e6-09f4900333bc` - Restore monitor on AWS instance using [Jenkins job](https://jenkins.scylladb.com/view/QA/job/QA-tools/job/hydra-show-monitor/parambuild/?test_id=050050a0-8ff6-4411-86e6-09f4900333bc) - Show all stored logs command: `$ hydra investigate show-logs 050050a0-8ff6-4411-86e6-09f4900333bc` ## Logs: - **db-cluster-050050a0.tar.gz** - [https://cloudius-jenkins-test.s3.amazonaws.com/050050a0-8ff6-4411-86e6-09f4900333bc/20240608_032314/db-cluster-050050a0.tar.gz](https://cloudius-jenkins-test.s3.amazonaws.com/050050a0-8ff6-4411-86e6-09f4900333bc/20240608_032314/db-cluster-050050a0.tar.gz) - **sct-runner-events-050050a0.tar.gz** - [https://cloudius-jenkins-test.s3.amazonaws.com/050050a0-8ff6-4411-86e6-09f4900333bc/20240608_032314/sct-runner-events-050050a0.tar.gz](https://cloudius-jenkins-test.s3.amazonaws.com/050050a0-8ff6-4411-86e6-09f4900333bc/20240608_032314/sct-runner-events-050050a0.tar.gz) - **sct-050050a0.log.tar.gz** - [https://cloudius-jenkins-test.s3.amazonaws.com/050050a0-8ff6-4411-86e6-09f4900333bc/20240608_032314/sct-050050a0.log.tar.gz](https://cloudius-jenkins-test.s3.amazonaws.com/050050a0-8ff6-4411-86e6-09f4900333bc/20240608_032314/sct-050050a0.log.tar.gz) - **loader-set-050050a0.tar.gz** - [https://cloudius-jenkins-test.s3.amazonaws.com/050050a0-8ff6-4411-86e6-09f4900333bc/20240608_032314/loader-set-050050a0.tar.gz](https://cloudius-jenkins-test.s3.amazonaws.com/050050a0-8ff6-4411-86e6-09f4900333bc/20240608_032314/loader-set-050050a0.tar.gz) - **monitor-set-050050a0.tar.gz** - [https://cloudius-jenkins-test.s3.amazonaws.com/050050a0-8ff6-4411-86e6-09f4900333bc/20240608_032314/monitor-set-050050a0.tar.gz](https://cloudius-jenkins-test.s3.amazonaws.com/050050a0-8ff6-4411-86e6-09f4900333bc/20240608_032314/monitor-set-050050a0.tar.gz) [Jenkins job URL](https://jenkins.scylladb.com/job/scylla-master/job/rolling-upgrade/job/rolling-upgrade-ubuntu20.04-test/195/) [Argus](https://argus.scylladb.com/test/97a03f7d-fd85-468c-8c23-a465f7693243/runs?additionalRuns[]=050050a0-8ff6-4411-86e6-09f4900333bc)