Skip to content

disrupt_truncate_large_partition nemesis failure with no attribute error #10562

Open
@grzywin

Description

@grzywin

Some time ago following PR was merged to SCT #10335 where among others verify_stress_thread method was introduced. Since then, during execution of longevity tests for Operator, one of the nemesis called disrupt_truncate_large_partition is failing with following error:

Traceback (most recent call last):
  File "/home/ubuntu/scylla-cluster-tests/sdcm/nemesis.py", line 5693, in wrapper
    result = method(*args[1:], **kwargs)
  File "/home/ubuntu/scylla-cluster-tests/sdcm/nemesis.py", line 2192, in disrupt_truncate_large_partition
    self.tester.verify_stress_thread(bench_thread, error_handler=self._nemesis_stress_failure_handler)
  File "/home/ubuntu/scylla-cluster-tests/sdcm/tester.py", line 2354, in verify_stress_thread
    error_handler(thread_pool, errors)
  File "/home/ubuntu/scylla-cluster-tests/sdcm/nemesis.py", line 2144, in _nemesis_stress_failure_handler
    raise NemesisStressFailure(
sdcm.exceptions.NemesisStressFailure: Aborting 'SisyphusMonkey' nemesis as stress command failed with the following errors:
 on node 'sct-loaders-eu-central-1-0': ["Stress command execution failed with: 'NoneType' object has no attribute 'closed'"]
 on node 'sct-loaders-eu-central-1-1': ["Stress command execution failed with: 'NoneType' object has no attribute 'closed'"]

Example test run:
https://argus.scylladb.com/tests/scylla-cluster-tests/44e7b05a-d33c-4623-8bfa-b3b190fa3f06

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions