redpanda-data / redpanda

Redpanda is a streaming data platform for developers. Kafka API compatible. 10x faster. No ZooKeeper. No JVM!
https://redpanda.com
9.42k stars 578 forks source link

CI Failure (key symptom) in `BucketScrubSelfTest.test_missing_segment` #17509

Open vbotbuildovich opened 5 months ago

vbotbuildovich commented 5 months ago

https://buildkite.com/redpanda/redpanda/builds/47056

Module: rptest.tests.services_self_test
Class: BucketScrubSelfTest
Method: test_missing_segment
Arguments: {
    "cloud_storage_type": 1
}
test_id:    BucketScrubSelfTest.test_missing_segment
status:     FAIL
run time:   90.391 seconds

RuntimeError('Expected an exception!')
Traceback (most recent call last):
  File "/opt/.ducktape-venv/lib/python3.10/site-packages/ducktape/tests/runner_client.py", line 184, in _do_run
    data = self.run_test()
  File "/opt/.ducktape-venv/lib/python3.10/site-packages/ducktape/tests/runner_client.py", line 276, in run_test
    return self.test_context.function(self.test)
  File "/opt/.ducktape-venv/lib/python3.10/site-packages/ducktape/mark/_mark.py", line 535, in wrapper
    return functools.partial(f, *args, **kwargs)(*w_args, **w_kwargs)
  File "/root/tests/rptest/services/cluster.py", line 104, in wrapped
    r = f(self, *args, **kwargs)
  File "/root/tests/rptest/tests/services_self_test.py", line 263, in test_missing_segment
    with expect_exception(RuntimeError, lambda e: "fatal" in str(e)):
  File "/usr/lib/python3.10/contextlib.py", line 142, in __exit__
    next(self.gen)
  File "/root/tests/rptest/util.py", line 305, in expect_exception
    raise RuntimeError("Expected an exception!")
RuntimeError: Expected an exception!

JIRA Link: CORE-1955

vbotbuildovich commented 5 months ago

*https://buildkite.com/redpanda/redpanda/builds/47127

vbotbuildovich commented 3 months ago

*https://buildkite.com/redpanda/redpanda/builds/49516

piyushredpanda commented 2 months ago

@abhijat does this test remain relevant with the scrubber rework?

nvartolomei commented 1 month ago

@piyushredpanda yes. The scrubber rework covers only S3. The test remains relevant at least for gcs (google), abs (azure), and the rest of s3-compatible services. Even if we cover gcs and abs, there is a long tail of s3-compatible services which don't support an inventory api... Including minio. This is long term roadmap question rather than short term scrubber rework question.


Re failure: Need to take a look in a more timely fashion. All logs are gone now.