You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Base Scylla version: 6.2.1-20241106.a3a0ffbcd015 with build-id 94e4419682b4191f7c37e2d6bf02f4fa7988dff3
Target Scylla version (or git commit hash): 6.3.0~dev-20241206.7e2875d6489d with build-id 5227dd2a3fce4d2beb83ec6c17d47ad2e8ba6f5c
Kernel Version: 6.8.0-1017-gcp
Issue description
Such an errors which occur during the rolling upgrade test may be ignored:
2024-12-07 06:44:14.987 <2024-12-07 06:44:12.541>: (DatabaseLogEvent Severity.ERROR) period_type=one-time event_id=afd96633-fe01-4632-a902-62cbc0a645e4: type=RUNTIME_ERROR regex=std::runtime_error line_number=135539 node=rolling-upgrade--ubuntu-focal-db-node-0bb842d4-0-3
2024-12-07T06:44:12.541+00:00 rolling-upgrade--ubuntu-focal-db-node-0bb842d4-0-3 !ERR | scylla[13464]: [shard 0: gms] raft_topology - drain rpc failed, proceed to fence old writes: std::runtime_error (raft topology: exec_global_command(barrier_and_drain) failed with seastar::rpc::closed_error (connection is closed))
Need some SCT workaround to handle/ignore such errors
Impact
No any impact, just enhancement for SCT is needed
How frequently does it reproduce?
Describe the frequency with how this issue can be reproduced.
OS / Image: https://www.googleapis.com/compute/v1/projects/scylla-images/global/images/scylladb-6-2-1 (gce: undefined_region)
Test: rolling-upgrade-gce-image-test
Test id: 0bb842d4-dff5-49a9-aa6a-abe328dcd1aa
Test name: scylla-master/rolling-upgrade/rolling-upgrade-gce-image-test
Test method: upgrade_test.UpgradeTest.test_rolling_upgrade
Test config file(s):
This error was not included to ignoring list. need new PR to update. @timtimb0t , please, add this template and run job several times to catch another possible error messages
Packages
Base Scylla version:
6.2.1-20241106.a3a0ffbcd015
with build-id94e4419682b4191f7c37e2d6bf02f4fa7988dff3
Target Scylla version (or git commit hash):
6.3.0~dev-20241206.7e2875d6489d
with build-id5227dd2a3fce4d2beb83ec6c17d47ad2e8ba6f5c
Kernel Version:
6.8.0-1017-gcp
Issue description
Such an errors which occur during the rolling upgrade test may be ignored:
Need some SCT workaround to handle/ignore such errors
Impact
No any impact, just enhancement for SCT is needed
How frequently does it reproduce?
Describe the frequency with how this issue can be reproduced.
Installation details
Cluster size: 4 nodes (n2-highmem-32)
Scylla Nodes used in this run:
OS / Image:
https://www.googleapis.com/compute/v1/projects/scylla-images/global/images/scylladb-6-2-1
(gce: undefined_region)Test:
rolling-upgrade-gce-image-test
Test id:
0bb842d4-dff5-49a9-aa6a-abe328dcd1aa
Test name:
scylla-master/rolling-upgrade/rolling-upgrade-gce-image-test
Test method:
upgrade_test.UpgradeTest.test_rolling_upgrade
Test config file(s):
Logs and commands
$ hydra investigate show-monitor 0bb842d4-dff5-49a9-aa6a-abe328dcd1aa
$ hydra investigate show-logs 0bb842d4-dff5-49a9-aa6a-abe328dcd1aa
Logs:
Jenkins job URL
Argus
The text was updated successfully, but these errors were encountered: