Julia Yakovlev

Results 37 issues of Julia Yakovlev

## Installation details Kernel Version: 5.15.0-1019-aws Scylla version (or git commit hash): `2022.2.0~rc1-20220902.a9bc6d191031` with build-id `074a0cb9e6a5ab36ba5e7f81385e68079ab6eeda` Cluster size: 4 nodes (i3.2xlarge) Scylla Nodes used in this run: - longevity-lwt-1loader-3h-2022-2-db-node-bacc08b7-4 (13.53.214.159...

bug
high

## Installation details Kernel Version: 5.15.0-1026-aws Scylla version (or git commit hash): `5.2.0~dev-20221210.e47794ed9832` with build-id `a0d3f077099c66bf6c75707e386c6be3ba2c431f` Cluster size: 4 nodes (i3en.3xlarge) Scylla Nodes used in this run: - longevity-large-collections-12h-mas-db-node-26dc39ad-5 (54.74.26.148...

type/bug
triage/master
triage/oss
P2

## Issue description - [ ] This issue is a regression. - [x] It is unknown if this issue is a regression. New added node remained in **`UJ` status** on...

triage/oss
P1

Add scylla-doctor to artifact test, run it and validate json output file. Task: https://github.com/scylladb/qa-tasks/issues/1617 ### Testing - [x] [artifacts-debian10-arm-test](https://argus.scylladb.com/test/55102838-2293-47d6-8bde-2ea1b27af077/runs?additionalRuns[]=6729e700-fc68-48a8-95a5-4f5cb8649084) - [x] [artifacts-centos8-test](https://argus.scylladb.com/test/e38d1306-708f-4d21-b0ef-d22c492d697d/runs?additionalRuns[]=5b823a42-e6d7-4301-9356-2a0741842dee) - [ ] [Azure](https://argus.scylladb.com/test/302cc48f-8148-485c-b327-1469dea7f8cf/runs?additionalRuns[]=62149cc3-c86f-4d69-a631-371875e88766) - issue https://github.com/scylladb/field-engineering/issues/2249 -...

Cover issue https://github.com/scylladb/scylladb/issues/16759 ### Testing - [ ] ### PR pre-checks (self review) - [ ] I added the relevant `backport` labels - [ ] I didn't leave commented-out/debugging code...

Enospace nemesis ran on `longevity-tls-50gb-3d-2023-1-db-node-e4715f1f-3` at about `2024-04-02 13:51` ``` < t:2024-04-02 13:51:27,189 f:wait.py l:52 c:sdcm.wait p:DEBUG > wait_for: Retrying Wait for new ENOSPC error occurs in database: attempt 4...

From time to time monitor creation fails despite the instance was created. Error: ``` < t:2024-03-06 20:54:36,659 f:gce_utils.py l:504 c:sdcm.utils.gce_utils p:DEBUG > Creating the rolling-upgrade--centos-8-monitor-node-aff52e4d-0-1 instance in us-east1-c... < t:2024-03-06...

GCE

`disrupt_sla_decrease_shares_during_load` ran in parallel with `disrupt_add_remove_dc`. `disrupt_add_remove_dc` nemesis adds a new node in a new DC and the removes it. `disrupt_sla_decrease_shares_during_load` failed with error: ``` (Node 10.4.3.76) - Service level...

SLA

`disrupt_sla_increase_shares_during_load` ran in parallel with `disrupt_restart_with_resharding` and failed with error `SchedulerGroupNotFound` on `longevity-sla-system-24h-2024-1-db-node-0f9f825b-4 ` node. ``` File "/home/ubuntu/scylla-cluster-tests/sdcm/sla/libs/sla_utils.py", line 410, in wait_for_service_level_propagated raise SchedulerGroupNotFound(f"Scheduler groups for {service_level.name} service levels is...

SLA

C-s load consistently timed out in the longevity-10gb-3h-gce test despite https://github.com/scylladb/scylla-cluster-tests/pull/7108 its soft timeout was increased. See discussion here https://argus.scylladb.com/test/23a9f4cc-4d94-42d4-a427-6ece4fd9a487/runs?additionalRuns[]=0899a8dd-bbd3-45c3-a8b8-df838402ca9d Looks like we need to investigate it ## Packages Scylla...